Re: [Idr] 2 week adoption call for draft-wang-idr-eag-distribution-02 (5/22 to 6/5)

"Susan Hares" <shares@ndzh.com> Fri, 22 May 2015 18:49 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3DDF1A0075 for <idr@ietfa.amsl.com>; Fri, 22 May 2015 11:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Level:
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q9613W7Vbh6k for <idr@ietfa.amsl.com>; Fri, 22 May 2015 11:49:29 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 352031A00C2 for <idr@ietf.org>; Fri, 22 May 2015 11:49:17 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.202.180;
From: Susan Hares <shares@ndzh.com>
To: "'Acee Lindem (acee)'" <acee@cisco.com>, 'Jeff Tantsura' <jeff.tantsura@ericsson.com>, idr@ietf.org
References: <006f01d09482$17c489c0$474d9d40$@ndzh.com> <D1849CBA.99EC1%jeff.tantsura@ericsson.com> <D184C8BF.1EF9C%acee@cisco.com>
In-Reply-To: <D184C8BF.1EF9C%acee@cisco.com>
Date: Fri, 22 May 2015 14:49:16 -0400
Message-ID: <01a401d094c0$013449a0$039cdce0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A5_01D0949E.7A273D80"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJnl2en9Oxu+22cQ5Mlnrvz6+xbOwK1JC2dAnhtwlCcMOSAAA==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/KFVZegSxxf3YZAVRYPqaVvsmJVc>
Subject: Re: [Idr] 2 week adoption call for draft-wang-idr-eag-distribution-02 (5/22 to 6/5)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 May 2015 18:49:30 -0000

Acee:

 

This sounds like a good idea. 

 

Sue 

 

From: Acee Lindem (acee) [mailto:acee@cisco.com] 
Sent: Friday, May 22, 2015 11:54 AM
To: Jeff Tantsura; Susan Hares; idr@ietf.org
Subject: Re: [Idr] 2 week adoption call for draft-wang-idr-eag-distribution-02 (5/22 to 6/5)

 

I support with one comment.

 

In the future, I’m wondering if we could standardize the BGP Link State encoding in the corresponding IGP documents? It seems like it would be possible since it is simply the TLV mapping and the  IANA code point(s). 

 

Thanks,

Acee

 

From: Jeff Tantsura <jeff.tantsura@ericsson.com>
Date: Friday, May 22, 2015 at 11:45 AM
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] 2 week adoption call for draft-wang-idr-eag-distribution-02 (5/22 to 6/5)

 

Support as co-author

 

Cheers,

Jeff

 

From: Susan Hares <shares@ndzh.com>
Date: Friday, May 22, 2015 at 4:26 AM
To: "idr@ietf.org" <idr@ietf.org>
Subject: [Idr] 2 week adoption call for draft-wang-idr-eag-distribution-02 (5/22 to 6/5)

 

This begins a 2 week Working Group adoption for draft-wang-idr-eag-distribution.   You can find the draft at: 

 

http://datatracker.ietf.org/doc/draft-wang-idr-eag-distribution/

 

This draft proposes a new BGP-LS 

 

   As MPLS-TE network grows, administrative Groups advertised as a
   fixed-length 32-bit Bitmask is quite constraining.  "Extended
   Administrative Group" IGP TE extensions sub-TLV defined in [RFC7308 <https://tools.ietf.org/html/rfc7308> ]
   is introduced to provide for additional administrative groups (link
   colors) beyond the current limit of 32.

 

 

   The EAG TLV is used in addition to the Administrative Groups when a
   node wants to advertise more than 32 colors for a link.  The EAG TLV
   is optional.  The format and semantics of the 'value' fields in EAG
   TLVs correspond to the format and semantics of value fields in IGP
   extension sub-TLVs, defined in [RFC7308 <https://tools.ietf.org/html/rfc7308> ].
 
   +------------+---------------------+--------------+-----------------+
   |  TLV Code  |     Description     |     IS-IS    |   Defined in:   |
   |    Point   |                     |  TLV/Sub-TLV |                 |
   +------------+---------------------+--------------+-----------------+
   |    xxxx    |       Extended      |     22/xx    |    [RFC7308 <https://tools.ietf.org/html/rfc7308> ]    |
   |            |      Admin Group    |              |                 |
   +------------+---------------------+--------------+-----------------+

 

Please in your comments include “support” or “no support” for this draft. 

 

Sue Hares and John Scudder.