Re: [OSPF] Fwd: Last Call: <draft-ietf-isis-l2bundles-04.txt> (Advertising L2 Bundle Member Link Attributes in IS-IS) to Proposed Standard

"Acee Lindem (acee)" <> Thu, 11 May 2017 20:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9AA7812F3D5; Thu, 11 May 2017 13:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cyhpJPewUcym; Thu, 11 May 2017 13:54:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CCCBD12E039; Thu, 11 May 2017 13:48:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=25873; q=dns/txt; s=iport; t=1494535720; x=1495745320; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=mKKSCPIx9+Gy+7wKVyykoKKVzBtigZ+zCR95p8DRO64=; b=fIkSfG9+ocXV9/4qpW9PYIiPB6l/QBjJ/j4y6D1hptpj5dXOLJF0fZ4o nTVU7yCKKQP6f/52pd8pgvK+77eEy+s0+cJeZrVTK5Fam/DVgTEDbEb9K 5+DpyPLQeZYXEr8Nmh3WSuOS6P5iGwM2ZJXDZ6bR+fE61KrXJwVjK8quv Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.38,325,1491264000"; d="scan'208,217";a="244217638"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 May 2017 20:48:39 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v4BKmdKK000994 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 11 May 2017 20:48:39 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 11 May 2017 16:48:38 -0400
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Thu, 11 May 2017 16:48:38 -0400
From: "Acee Lindem (acee)" <>
To: "Les Ginsberg (ginsberg)" <>, Alia Atlas <>, OSPF List <>, "" <>, "idr@ietf. org" <>
Thread-Topic: [OSPF] Fwd: Last Call: <draft-ietf-isis-l2bundles-04.txt> (Advertising L2 Bundle Member Link Attributes in IS-IS) to Proposed Standard
Thread-Index: AQHSxDuzUjI6VH7keUqjK/l8NUEI7aHviKoAgABeFwD//8CwAA==
Date: Thu, 11 May 2017 20:48:38 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D53A461CAEA63aceeciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [OSPF] Fwd: Last Call: <draft-ietf-isis-l2bundles-04.txt> (Advertising L2 Bundle Member Link Attributes in IS-IS) to Proposed Standard
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 May 2017 20:54:30 -0000

Hi Les,

From: "Les Ginsberg (ginsberg)" <<>>
Date: Thursday, May 11, 2017 at 4:35 PM
To: Acee Lindem <<>>, Alia Atlas <<>>, OSPF WG List <<>>, Routing WG <<>>, IDR List <<>>
Subject: RE: [OSPF] Fwd: Last Call: <draft-ietf-isis-l2bundles-04.txt> (Advertising L2 Bundle Member Link Attributes in IS-IS) to Proposed Standard

Acee –

Did you look at the Appendix – which has ASCII art for some example encodings?

No  - I missed these. I was looking more for the format in body rather than just field descriptions. However, the examples are also helpful.



From: rtgwg [] On Behalf Of Acee Lindem (acee)
Sent: Thursday, May 11, 2017 11:58 AM
To: Alia Atlas; OSPF List;<>; idr@ietf. org
Subject: Re: [OSPF] Fwd: Last Call: <draft-ietf-isis-l2bundles-04.txt> (Advertising L2 Bundle Member Link Attributes in IS-IS) to Proposed Standard

Hi Alia,
I have reviewed the document and had several conversations with the authors. I believe the encodings are adaptable to the OSPF Segment Routing extensions. Of course, we’ll use a different identifier than System ID (Used to identify LAN-Adj-SID neighors). One comment I have is that it would be nice to have ASCII art graphically depicting the format of the new Sub-TLVs.


From: OSPF <<>> on behalf of Alia Atlas <<>>
Date: Wednesday, May 3, 2017 at 2:30 PM
To: OSPF WG List <<>>, Routing WG <<>>, IDR List <<>>
Subject: [OSPF] Fwd: Last Call: <draft-ietf-isis-l2bundles-04.txt> (Advertising L2 Bundle Member Link Attributes in IS-IS) to Proposed Standard


I'd like to bring this IETF Last Call to your attention.  The method for advertising
L2 bundle information via IS-IS described in this draft may be of interest for other
protocols (OSPF,  BGP-LS) that may use it as precedent for how to advertise
such information if there is need in the future and consistency is desired at that point.


---------- Forwarded message ----------
From: The IESG <<>>
Date: Wed, May 3, 2017 at 1:52 PM
Subject: Last Call: <draft-ietf-isis-l2bundles-04.txt> (Advertising L2 Bundle Member Link Attributes in IS-IS) to Proposed Standard
To: IETF-Announce <<>>

The IESG has received a request from the IS-IS for IP Internets WG (isis)
to consider the following document:
- 'Advertising L2 Bundle Member Link Attributes in IS-IS'
  <draft-ietf-isis-l2bundles-04.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the<> mailing lists by 2017-05-17. Exceptionally, comments may be
sent to<> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   There are deployments where the Layer 3 interface on which IS-IS
   operates is a Layer 2 interface bundle.  Existing IS-IS
   advertisements only support advertising link attributes of the Layer
   3 interface.  If entities external to IS-IS wish to control traffic
   flows on the individual physical links which comprise the Layer 2
   interface bundle link attribute information about the bundle members
   is required.

   This document introduces the ability for IS-IS to advertise the link
   attributes of layer 2 (L2) bundle members.

The file can be obtained via

IESG discussion can be tracked via

The following IPR Declarations may be related to this I-D: