Re: [Isis-wg] I-D Action:draft-ietf-isis-layer2-11.txt

Xiaohu

This is something that should have been proposed months ago.

The document is in the RFC editor's queue, and this change would require
it to go back to the working group, something which I would not be
prepared to do unless that is the consensus of both working groups
affected.

Stewart

On 28/02/2011 02:59, Xu Xiaohu wrote:
> Hi all,
>
> As I heard from some could data center operators, 4096 VLANs would not be
> enough for isolating the huge amount of tenants in their future data center
> networks. Besides, the VLAN translation is a desirable feature in some
> scenarios (e.g., the same VLAN ID in different parts of the data center
> network is used for different tenants while different VLAN IDs in different
> parts of the data center network are used to connect a single tenant).
>
> Hence, I wonder whether it is possible to replace the fixed-length VLAN ID
> field (e.g., the VLAN-ID field in the MAC-reachability TLV as shown below)
> with a tenant/VPN instance ID TLV. With such TLV, at least the two problems
> mentioned above can be solved easily. 
>
> Best wishes,
> Xiaohu
>
> ========================================================================
> 2.1.  The MAC-Reachability TLV
>
>    The MAC-Reachability (MAC-RI) TLV is IS-IS TLV type 141 and has the
>    following format:
>
>    +-+-+-+-+-+-+-+-+
>    | Type= MAC-RI  |                  (1 byte)
>    +-+-+-+-+-+-+-+-+
>    |   Length      |                  (1 byte)
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |   Topology-Id/ Nickname       |  (2 bytes)
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |   Confidence  |                  (1 byte)
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |  RESV |      VLAN-ID          |  (2 bytes)
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                          MAC (1)    (6 bytes)                 |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                   .................                           |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                          MAC (N)    (6 bytes)                 |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>
>> -----邮件原件-----
>> 发件人: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] 代表
>> Internet-Drafts@ietf.org
>> 发送时间: 2011年2月10日 4:00
>> 收件人: i-d-announce@ietf.org
>> 抄送: isis-wg@ietf.org
>> 主题: [Isis-wg] I-D Action:draft-ietf-isis-layer2-11.txt
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the IS-IS for IP Internets Working Group of
> the
>> IETF.
>>
>>
>> 	Title           : Extensions to IS-IS for Layer-2 Systems
>> 	Author(s)       : A. Banerjee, D. Ward
>> 	Filename        : draft-ietf-isis-layer2-11.txt
>> 	Pages           : 11
>> 	Date            : 2011-02-09
>>
>> This document specifies the Intermediate System to Intermediate
>> System (IS-IS) extensions necessary to support link state routing for
>> any protocols running directly over Layer-2.  While supporting this
>> concept involves several pieces, this document only describes
>> extensions to IS-IS.  Furthermore, the Type, Length, Value pairs
>> (TLVs) described in this document are generic Layer-2 additions and
>> specific ones as needed are defined in the IS-IS technology specific
>> extensions.  We leave it to the systems using these IS-IS extensions
>> to explain how the information carried in IS-IS is used.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-isis-layer2-11.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg

-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html