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)" <ginsberg@cisco.com> Thu, 11 May 2017 20:40 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A7F91314F4; Thu, 11 May 2017 13:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 Wu_6FlZZeDwD; Thu, 11 May 2017 13:40:20 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3658312EC44; Thu, 11 May 2017 13:35:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; 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-Anti-Spam-Result: =?us-ascii?q?A0CrAQAg4xNZ/5NdJa1TChoBAQEBAgEBA?= =?us-ascii?q?QEIAQEBAYJuPCtigQwHg2KKGJFYiCWIF4U4gg8shXgCGoRoPxgBAgEBAQEBAQF?= =?us-ascii?q?rKIUVAQEBAQMjCkEbAgEIEQMBAQEkBAMCAgIfERQJCAIEARIIigADFQ6xUYImh?= =?us-ascii?q?zANgzgBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYZfgV0BgxuCVIFnPwkGEIJcgmA?= =?us-ascii?q?Fhw+CNZQLOwGHG4ZhS4RKgg2FO4osiy2JFQEfOIEKcBVGhHYcGYFKdogMgQ0BA?= =?us-ascii?q?QE?=
X-IronPort-AV: E=Sophos; i="5.38,322,1491264000"; d="scan'208,217"; a="26245520"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 May 2017 20:35:11 +0000
Received: from xch-rcd-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by rcdn-core-11.cisco.com (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 xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 11 May 2017 15:35:10 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Thu, 11 May 2017 15:35:10 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, Alia Atlas <akatlas@gmail.com>, OSPF List <ospf@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "idr@ietf. org" <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: <a9a5d7223f0448cd8fa55bb1413769fb@XCH-ALN-001.cisco.com>
References: <149383397646.4894.14546129703556603533.idtracker@ietfa.amsl.com> <CAG4d1rczZxneWek03rnp+1GqQdwJfMg5h-wLGkB+aEutrTP5eg@mail.gmail.com> <D53A2B68.AEA33%acee@cisco.com>
In-Reply-To: <D53A2B68.AEA33%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.152.12]
Content-Type: multipart/alternative; boundary="_000_a9a5d7223f0448cd8fa55bb1413769fbXCHALN001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/pEUl7uYzfOgCjbgZWzlGw1aq8oM>
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-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=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?

   Les


From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Thursday, May 11, 2017 11:58 AM
To: Alia Atlas; OSPF List; rtgwg@ietf.org; 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.

Thanks,
Acee

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

Dear RTGWG, OSPF WG & IDR WG,

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.

Regards,
Alia


---------- Forwarded message ----------
From: The IESG <iesg-secretary@ietf.org<mailto:iesg-secretary@ietf.org>>
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 <ietf-announce@ietf.org<mailto:ietf-announce@ietf.org>>
Cc: hannes@gredler.at<mailto:hannes@gredler.at>, isis-chairs@ietf.org<mailto:isis-chairs@ietf.org>, isis-wg@ietf.org<mailto:isis-wg@ietf.org>, draft-ietf-isis-l2bundles@ietf.org<mailto:draft-ietf-isis-l2bundles@ietf.org>, akatlas@gmail.com<mailto:akatlas@gmail.com>



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
ietf@ietf.org<mailto:ietf@ietf.org> mailing lists by 2017-05-17. Exceptionally, comments may be
sent to iesg@ietf.org<mailto:iesg@ietf.org> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   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
https://datatracker.ietf.org/doc/draft-ietf-isis-l2bundles/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-isis-l2bundles/ballot/

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

   https://datatracker.ietf.org/ipr/2793/