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

"Les Ginsberg (ginsberg)" <> Thu, 11 May 2017 20:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6A7F91314F4; Thu, 11 May 2017 13:40:22 -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 Wu_6FlZZeDwD; Thu, 11 May 2017 13:40:20 -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 3658312EC44; Thu, 11 May 2017 13:35:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=22020; q=dns/txt; s=iport; t=1494534912; x=1495744512; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=goLi8dJoZWgsmusR6kLM5nSkyTrfiCBysLF+wu9oLGs=; b=HDmbDcr+dRAGDPGVTp4qnSwFC8DpzG2xy2b0DzwUqRtBZsKH+V0Kf/fc ZgaYzDxD4EsUNXuqTbdTSv6EeLuRzTXS+gnhepxYl9y1BQpylgUmaTlYE tetSMjjhAR2kabpgIaYl/XirthwrptoKQNMj1NXC25PQRmynxO2FwNToU M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.38,322,1491264000"; d="scan'208,217"; a="26245520"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 May 2017 20:35:11 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v4BKZBE9006150 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 11 May 2017 20:35:11 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 11 May 2017 15:35:10 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Thu, 11 May 2017 15:35:10 -0500
From: "Les Ginsberg (ginsberg)" <>
To: "Acee Lindem (acee)" <>, 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: AQHSxDYf4022tm3LG0qAyWk0ibB7oaHjQiMAgAyaaAD//8b+0A==
Date: Thu, 11 May 2017 20:35:10 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_a9a5d7223f0448cd8fa55bb1413769fbXCHALN001ciscocom_"
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:40:23 -0000

Acee –

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


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: