From nobody Mon Oct 3 13:59:54 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6228112955C; Mon, 3 Oct 2016 13:59:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.321 X-Spam-Level: X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 GG2ILKheruAO; Mon, 3 Oct 2016 13:59:37 -0700 (PDT) Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98764129545; Mon, 3 Oct 2016 13:59:37 -0700 (PDT) X-AuditID: c6180641-2580a98000000a0b-e0-57f27253e9cb Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by (Symantec Mail Security) with SMTP id 54.43.02571.35272F75; Mon, 3 Oct 2016 16:59:32 +0200 (CEST) Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0319.002; Mon, 3 Oct 2016 16:59:33 -0400 From: David Allan I To: "pim@ietf.org" , "spring@ietf.org" , "isis-wg@ietf.org list (isis-wg@ietf.org)" , "ospf@ietf.org" Thread-Topic: Computed Multicast for SPRING Thread-Index: AdIduB2jNC5K4CNdTs24IypOvIp7Zw== Date: Mon, 3 Oct 2016 20:59:32 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.10] Content-Type: multipart/alternative; boundary="_000_E6C17D2345AC7A45B7D054D407AA205C4BDDB302eusaamb105erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBLMWRmVeSWpSXmKPExsUyuXRPlG5I0adwg5krBSyOHnrPatFy7x67 xZeHN5ktjl/4zejA4rFkyU+mAMYoLpuU1JzMstQifbsErowj/3+zF8yXqvj87y5zA+MW8S5G Dg4JAROJ88+kuxi5OIQENjBKbF/dwAzhLGOUeLjpH1MXIycHm4CBxJ7/XxhBbBGBVYwSf3r9 QGxhATWJeTdvs0HEtSUOLz3JCmHrSRy4uBfMZhFQkbh/9hGYzSvgK7H//VV2EJtRQEzi+6k1 YPOZBcQlbj2ZD2ZLCAhILNlznhnCFpV4+fgfK4StJDFp6TlWiPp8iTUPIG7jFRCUODnzCcsE RsFZSEbNQlI2C0kZRFxHYsHuT2wQtrbEsoWvmWHsMwceMyGLL2BkX8XIUVpckJObbmS4iREY /sck2Bx3MO7t9TzEKMDBqMTDq6DzKVyINbGsuDL3EKMEB7OSCK/JUaAQb0piZVVqUX58UWlO avEhRmkOFiVx3ush98OFBNITS1KzU1MLUotgskwcnFINjCn7pi4x5t6x7VKkxj6/jyZGivHy jQHbY0R/v9r0aqr/439hOcpNS5ds9zyi8PmM4Rruj3FTV8oV/N+ZJb/LQFbF8HLR1LyJJ7dF sDc3pz9qSpe1nBV/b6P2hSNdmhO4IhyvzudcGrZridb7gx82neWZWmEwUXZLuJWe8pT13mv2 VPA93mC1/70SS3FGoqEWc1FxIgBnF3lnewIAAA== Archived-At: Subject: [Isis-wg] Computed Multicast for SPRING X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 20:59:40 -0000 --_000_E6C17D2345AC7A45B7D054D407AA205C4BDDB302eusaamb105erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable HI Folks: For those interested in the subject, we've assembled a tutorial as a compan= ion to version 2 of the framework draft (draft-allan-spring-mpls-multicast-= framework-02), that explains the approach and the algorithm in much greater= detail. It is available here: http://standards.ericsson.com/mpls/SPRING_Multicast_Tutorial_v4.pdf As always comments and questions are very welcome.... Cheers Dave --_000_E6C17D2345AC7A45B7D054D407AA205C4BDDB302eusaamb105erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

HI Folks:

 

For those interested in the subject, we’ve ass= embled a tutorial as a companion to version 2 of the framework draft (draft= -allan-spring-mpls-multicast-framework-02), that explains the approach and = the algorithm in much greater detail.

 

It is available here:

http://standards.ericsson.com/mpls/SPRING_Multi= cast_Tutorial_v4.pdf

 

As always comments and questions are very welcome= 230;.

 

Cheers

Dave

--_000_E6C17D2345AC7A45B7D054D407AA205C4BDDB302eusaamb105erics_-- From nobody Thu Oct 13 03:09:42 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A9B61295D2; Thu, 13 Oct 2016 03:09:40 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.34.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147635338062.2870.1197392228536492520.idtracker@ietfa.amsl.com> Date: Thu, 13 Oct 2016 03:09:40 -0700 Archived-At: Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-08.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2016 10:09:40 -0000 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 of the IETF. Title : IS-IS Extensions for Segment Routing Authors : Stefano Previdi Clarence Filsfils Ahmed Bashandy Hannes Gredler Stephane Litkowski Bruno Decraene Jeff Tantsura Filename : draft-ietf-isis-segment-routing-extensions-08.txt Pages : 40 Date : 2016-10-13 Abstract: Segment Routing (SR) allows for a flexible definition of end-to-end paths within IGP topologies by encoding paths as sequences of topological sub-paths, called "segments". These segments are advertised by the link-state routing protocols (IS-IS and OSPF). This draft describes the necessary IS-IS extensions that need to be introduced for Segment Routing. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-segment-routing-extensions-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Oct 13 03:11:21 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AC72129728 for ; Thu, 13 Oct 2016 03:11:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.517 X-Spam-Level: X-Spam-Status: No, score=-17.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, 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 4HyWg8Byyq9R for ; Thu, 13 Oct 2016 03:11:18 -0700 (PDT) Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA8F3129727 for ; Thu, 13 Oct 2016 03:11:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2250; q=dns/txt; s=iport; t=1476353478; x=1477563078; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Bl5aQmYY9PA5ath9ZZPrM9jiWZL4P1sUpjMWHVNTwHk=; b=HLw6E6qF/kgUL9yI+SBRxlgTnWrEOPC7DyWdgi4vo38gMffYpIawjqcw euYpdOqO0tMbOfojDpG1Ou+Z2DFYwVAo+42mNSlqBJNLdfeb7MrWROU1+ 3IsXNLFtASFAUpBxksSJ+L+btIO8yJO7VCVgS37WV5aJu5btZ+S9BQpK+ g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ATAQAPXf9X/4YNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzwBAQEBAR1XfAeNLZcElDSCChwNhXgCggM4FAECAQEBAQEBAV4?= =?us-ascii?q?nhGEBAQEDAQEBATc0EAsCAQgYHhAnCyUCBBOISAgOwxkBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEdhj2BfQiCUIRHgzCCLwWUKIVaAYYmiVaBbk6EGYkgjHmDfgEeNlC?= =?us-ascii?q?EZHKHZIEAAQEB?= X-IronPort-AV: E=Sophos;i="5.31,339,1473120000"; d="scan'208";a="333326971" Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Oct 2016 10:11:17 +0000 Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u9DABH9H001751 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Thu, 13 Oct 2016 10:11:17 GMT Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-010.cisco.com (64.101.220.150) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 13 Oct 2016 06:11:17 -0400 Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Thu, 13 Oct 2016 06:11:16 -0400 From: "Stefano Previdi (sprevidi)" To: "isis-wg@ietf.org list" Thread-Topic: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-08.txt Thread-Index: AQHSJToi6Jt8zP9pDE+fYFks8UCgMQ== Date: Thu, 13 Oct 2016 10:11:16 +0000 Message-ID: <1FB9633E-BC6C-4155-BA0E-A53789AD9BA4@cisco.com> References: <147635338062.2870.1197392228536492520.idtracker@ietfa.amsl.com> In-Reply-To: <147635338062.2870.1197392228536492520.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.61.164.239] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-08.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2016 10:11:20 -0000 All, we added a new section describing the SRLB SubTLV.=20 This is a new capability for a SR enabled router: the ability to advertise = a label range used for local label allocation. Let me know any comment. Thanks. s. > On Oct 13, 2016, at 12:09 PM, internet-drafts@ietf.org wrote: >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the IS-IS for IP Internets of the IETF. >=20 > Title : IS-IS Extensions for Segment Routing > Authors : Stefano Previdi > Clarence Filsfils > Ahmed Bashandy > Hannes Gredler > Stephane Litkowski > Bruno Decraene > Jeff Tantsura > Filename : draft-ietf-isis-segment-routing-extensions-08.txt > Pages : 40 > Date : 2016-10-13 >=20 > Abstract: > Segment Routing (SR) allows for a flexible definition of end-to-end > paths within IGP topologies by encoding paths as sequences of > topological sub-paths, called "segments". These segments are > advertised by the link-state routing protocols (IS-IS and OSPF). >=20 > This draft describes the necessary IS-IS extensions that need to be > introduced for Segment Routing. >=20 >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensio= ns/ >=20 > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-08 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-isis-segment-routing-exten= sions-08 >=20 >=20 > Please note that it may take a couple of minutes from the time of submiss= ion > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg From nobody Fri Oct 14 02:32:45 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB6412947F; Fri, 14 Oct 2016 02:32:44 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.34.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147643756405.18669.10353570368417885149.idtracker@ietfa.amsl.com> Date: Fri, 14 Oct 2016 02:32:44 -0700 Archived-At: Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D Action: draft-ietf-isis-mpls-elc-02.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2016 09:32:44 -0000 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 of the IETF. Title : Signaling Entropy Label Capability Using IS-IS Authors : Xiaohu Xu Sriganesh Kini Siva Sivabalan Clarence Filsfils Stephane Litkowski Filename : draft-ietf-isis-mpls-elc-02.txt Pages : 6 Date : 2016-10-14 Abstract: Multi Protocol Label Switching (MPLS) has defined a mechanism to load balance traffic flows using Entropy Labels (EL). An ingress LSR cannot insert ELs for packets going into a given tunnel unless an egress LSR has indicated via signaling that it can process ELs on that tunnel. This draft defines a mechanism to signal that capability using IS-IS. This mechanism is useful when the label advertisement is also done via IS-IS. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-isis-mpls-elc/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-mpls-elc-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Oct 17 08:42:22 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73EC81295BF for ; Mon, 17 Oct 2016 08:42:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.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 xZNWqE5bIL0w for ; Mon, 17 Oct 2016 08:42:17 -0700 (PDT) Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0115.outbound.protection.outlook.com [104.47.42.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25D4012941E for ; Mon, 17 Oct 2016 08:42:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=GyWjVFjnBnA26Ta6o/bqAk6H7VevTPG61bT2nUoFoDc=; b=KOtW8jPcbeftccRIbKsUaud6zlSyjJJGBhkhNettZKiPlIax5ajzVfzeO6amuSVWeVvuV1bN6P6F31JnWBm9TPB3gCdXtBdMdDSIIesk5DMowXyxrwDJd/pvm39/hElsA6yBk5cnjXe8oU2oFAEMuZRN12mqiwGLwUQeB+y1HJo= Received: from MWHPR05MB2829.namprd05.prod.outlook.com (10.168.245.11) by MWHPR05MB2832.namprd05.prod.outlook.com (10.168.245.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.5; Mon, 17 Oct 2016 15:42:14 +0000 Received: from MWHPR05MB2829.namprd05.prod.outlook.com ([10.168.245.11]) by MWHPR05MB2829.namprd05.prod.outlook.com ([10.168.245.11]) with mapi id 15.01.0669.018; Mon, 17 Oct 2016 15:42:14 +0000 From: Chris Bowers To: ISIS-WG Thread-Topic: removing Controlled Convergence sub-TLV from draft-ietf-isis-mrt-02 Thread-Index: AdIoinEwvgg0c8IhSPibxPBzdXrJow== Date: Mon, 17 Oct 2016 15:42:14 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=cbowers@juniper.net; x-originating-ip: [66.129.239.13] x-ms-office365-filtering-correlation-id: 9447a418-1aa7-4d63-ea53-08d3f6a42b13 x-microsoft-exchange-diagnostics: 1; MWHPR05MB2832; 7:NVXcPMjFGioQbfdUxHtHd/dE+OfcKKhCijK6vl+uh8FB5ECPx4oydW/AdnMcMWpfMZnhjpOBP3JV3TYPnZixvM5nRI1AvBKUiGdPI6stn8V+mP/G8nJQvn0tORMCul0Jw+adZ+wVVvDlVjM6MWFT4rUI3vZ7BcFVe5GD9iLkjST7IDQRaO+C3Sb5Hr1ufBaFjgsczVkVu9XXA+PtVNbEN5p10B1tf+Q93LqBVuWITRcw7BpE/DDZwFkp5CokAJbrqIxYeYcuzrXd7KrWkuKUhu6aQ2xn4/qxxgq0JaYCsIzt/EjJcWmn4J7n6dJZ+TqJBeCA23z4ZZgUFoy2I90Cu90gUjokWjp+pSvosHT2cqg= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:MWHPR05MB2832; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(278428928389397)(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026); SRVR:MWHPR05MB2832; BCL:0; PCL:0; RULEID:; SRVR:MWHPR05MB2832; x-forefront-prvs: 0098BA6C6C x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(189002)(199003)(68736007)(2906002)(10400500002)(76576001)(77096005)(92566002)(2900100001)(11100500001)(8936002)(9686002)(33656002)(6916009)(81156014)(54356999)(81166006)(8676002)(50986999)(101416001)(3846002)(586003)(6116002)(122556002)(5002640100001)(102836003)(189998001)(110136003)(3660700001)(7696004)(3280700002)(229853001)(74316002)(106356001)(105586002)(99286002)(97736004)(450100001)(5660300001)(107886002)(87936001)(66066001)(305945005)(86362001)(15975445007)(7846002)(7736002)(19580395003)(230783001); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR05MB2832; H:MWHPR05MB2829.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_MWHPR05MB28293A6C72B7E545837B8E24A9D00MWHPR05MB2829namp_" MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Oct 2016 15:42:14.5155 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR05MB2832 Archived-At: Subject: [Isis-wg] removing Controlled Convergence sub-TLV from draft-ietf-isis-mrt-02 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2016 15:42:19 -0000 --_000_MWHPR05MB28293A6C72B7E545837B8E24A9D00MWHPR05MB2829namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable ISIS WG, The authors of draft-ietf-isis-mrt-02 are planning to remove the Controlle= d Convergence sub-TLV that draft, and instead use on an equivalent extension being defined in: https://tools.ietf.org/html/draft-bryant-rtgwg-param-sync-00 Since the Controlled Convergence sub-TLV communicates information that may = be useful for applications other that MRT, it makes sense to have it in a separate docume= nt to allow it to be better vetted in the context of those other applications. I don't think that anyone has implemented the Controlled Convergence sub-TL= V in draft-ietf-isis-mrt-02. But if this is not the case, or anyone has another objection to removing it= from draft-ietf-isis-mrt-02, please raise that objection in the next week or so. Thanks, Chris --_000_MWHPR05MB28293A6C72B7E545837B8E24A9D00MWHPR05MB2829namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
ISIS WG,
 
The authors of draft-ietf-isis-mrt-02  are planning to remove the= Controlled Convergence sub-TLV that draft,
and instead use on an equivalent extension being defined in:
 
 
Since the Controlled Convergence sub-TLV communicates information that= may be useful for
applications other that MRT, it makes sense to have it in a separate d= ocument to allow it to be
better vetted in the context of those other applications. 
 
I don’t think that anyone has implemented the Controlled Converg= ence sub-TLV in draft-ietf-isis-mrt-02. 
But if this is not the case, or anyone has another objection to removi= ng it from draft-ietf-isis-mrt-02, please
raise that objection in the next week or so.
 
Thanks,
Chris
 
 
--_000_MWHPR05MB28293A6C72B7E545837B8E24A9D00MWHPR05MB2829namp_-- From nobody Mon Oct 17 08:56:18 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DB029129881; Mon, 17 Oct 2016 08:56:11 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.34.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147671977189.4560.5334915334309363131.idtracker@ietfa.amsl.com> Date: Mon, 17 Oct 2016 08:56:11 -0700 Archived-At: Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D Action: draft-ietf-isis-yang-isis-cfg-12.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2016 15:56:12 -0000 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 of the IETF. Title : YANG Data Model for IS-IS protocol Authors : Stephane Litkowski Derek Yeung Acee Lindem Jeffrey Zhang Ladislav Lhotka Filename : draft-ietf-isis-yang-isis-cfg-12.txt Pages : 123 Date : 2016-10-17 Abstract: This document defines a YANG data model that can be used to configure and manage IS-IS protocol on network elements. It also defined an extension module for segment routing configuration and operation. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-isis-yang-isis-cfg/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-isis-yang-isis-cfg-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-yang-isis-cfg-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Oct 18 14:33:11 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8731298A0 for ; Tue, 18 Oct 2016 14:33:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 KRjaoFRupjbE for ; Tue, 18 Oct 2016 14:33:07 -0700 (PDT) Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a07:2ec0:2185::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DE3312989F for ; Tue, 18 Oct 2016 14:33:07 -0700 (PDT) Received: from equinox by eidolon.nox.tf with local (Exim 4.87) (envelope-from ) id 1bwc07-003OEt-Ar; Tue, 18 Oct 2016 23:33:02 +0200 Date: Tue, 18 Oct 2016 23:32:47 +0200 From: David Lamparter To: "isis-wg@ietf.org list (isis-wg@ietf.org)" , isis-chairs@tools.ietf.org Message-ID: <20161018213247.GQ639535@eidolon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) Archived-At: Cc: FredBaker.IETF@gmail.com Subject: [Isis-wg] Requesting WG adoption of draft-baker-ipv6-isis-dst-src-routing-06 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 21:33:10 -0000 Hello IS-IS wg, I'd like to request/suggest WG adoption of draft-baker-ipv6-isis-dst-src-routing-06 [https://datatracker.ietf.org/doc/draft-baker-ipv6-isis-dst-src-routing/] which describes the IS-IS bits of source/destination routing and would also like to head for early-allocation[*] of codepoints and MTID values (all marked "TBD" in the document). The rtgwg counterpart, draft-ietf-rtgwg-dst-src-routing[-02], was adopted by rtgwg a year ago. I'm also unaware of any IPR related to this draft, responding "no" to the boilerplate according to RFC 6702 Appendix A.3 :) The -06 version is identical to -05 except for updating Fred's author block. I don't expect significant changes in protocol operation and am unaware of open feedback in that direction (thus also the early-allocation request). As there haven't been any changes I'm unsure whether I should re-present the document; it'd probably end up being a repeat wasting people's time but I'd be happy to bring it up... Cheers, -David [*] early-allocation seems to not apply for blocks under "Expert Review" procedure, not sure if there is a process there? From nobody Tue Oct 18 14:35:08 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E368129890 for ; Tue, 18 Oct 2016 14:35:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 1bcKQw8DaMeA for ; Tue, 18 Oct 2016 14:35:05 -0700 (PDT) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2732E129695 for ; Tue, 18 Oct 2016 14:35:05 -0700 (PDT) Received: by mail-oi0-x22c.google.com with SMTP id y2so8733776oie.0 for ; Tue, 18 Oct 2016 14:35:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=WFADc7yV32YkZIqUFz/qDvdIwLBQR4+H7Usu0QKLGio=; b=HJoDvOF+CCZdPaHJ+HgDwBqj1oFXp/ZTmXphpdt7k/eLzT4XQEh4ofR1NAAPTh1i8k RK1lhP54obD+5I22wdVqDtdVMSc+P9nijJtf+x5miP1I4ANKKEAOA+wwJIzBt3hG3cWA mi2CBZvlchLpwA12AuL4q3f1omJJf6vEhjd0Sj5dDTKc0iOpokUvAgAOWWdWB4LuD8h/ xOerxwKxaMq0OJVqeHwA/nP3l1dMAcFkSDnasjayiVO82fQsv0Qub1VoOmAZwjxgYJVG E7spZAbf1aJHTSJTguGgPcrIrcDErEXUGImPSWVDfmYv0A9KM6vJ47VgICwpmXO9aSP7 i/QA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=WFADc7yV32YkZIqUFz/qDvdIwLBQR4+H7Usu0QKLGio=; b=dkDTjPyR2v/86W5VscsIhIXftdF1S94yDmTVxhrqWcFlwRtOcJBBEVFv1MvgWl0zFR 9Ml/tpbeWtRczn0H6kz59hZmf6czMcFxz8vQG7gW/5BiPfACsi0iYlsrA3HXnHTSB0pZ SqiNTMud01Ac/MPZ7QFTTwuSZu7pf5lBxn1QUhPblNRp2E180ENQxRhYR+2Rv9oyBmNn oN2huLYnfMaEQGkklvtW68/Zz0xYOtSdI2J3kVPZIgxZzLCGTZHpVuvvC4cRV9vYVajm Z84ZEDiTjNJ/zMU2buHIqF10d7o5V1m2zx2ZQBSBLBMhmxQRCOKjTxmt2U+V/lLOaFFC Ut9A== X-Gm-Message-State: AA6/9Rm5PacMbpMNaR3R16apX20H7pgPmyJF8a8KP2Jr/qb/39Idx7QlZWsPpgwIvc80kg== X-Received: by 10.202.56.132 with SMTP id f126mr2146616oia.73.1476826504578; Tue, 18 Oct 2016 14:35:04 -0700 (PDT) Received: from [10.0.2.8] (wsip-184-191-158-196.sd.sd.cox.net. [184.191.158.196]) by smtp.gmail.com with ESMTPSA id f36sm13387832otf.17.2016.10.18.14.35.03 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 18 Oct 2016 14:35:03 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Fred Baker In-Reply-To: <20161018213247.GQ639535@eidolon> Date: Tue, 18 Oct 2016 14:35:01 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <6DB53EDB-1FDE-4B39-922B-0BABF319408A@gmail.com> References: <20161018213247.GQ639535@eidolon> To: David Lamparter X-Mailer: Apple Mail (2.3124) Archived-At: Cc: isis-chairs@tools.ietf.org, "isis-wg@ietf.org list \(isis-wg@ietf.org\)" Subject: Re: [Isis-wg] Requesting WG adoption of draft-baker-ipv6-isis-dst-src-routing-06 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 21:35:07 -0000 I would similarly favor working group adoption. I do not plan to be in = Seoul at this time, but would be happy to engage in mailer discussion. > On Oct 18, 2016, at 2:32 PM, David Lamparter = wrote: >=20 > Hello IS-IS wg, >=20 >=20 > I'd like to request/suggest WG adoption of >=20 > draft-baker-ipv6-isis-dst-src-routing-06 >=20 > = [https://datatracker.ietf.org/doc/draft-baker-ipv6-isis-dst-src-routing/] >=20 > which describes the IS-IS bits of source/destination routing and would > also like to head for early-allocation[*] of codepoints and MTID = values > (all marked "TBD" in the document). The rtgwg counterpart, > draft-ietf-rtgwg-dst-src-routing[-02], was adopted by rtgwg a year = ago. >=20 > I'm also unaware of any IPR related to this draft, responding "no" to > the boilerplate according to RFC 6702 Appendix A.3 :) >=20 > The -06 version is identical to -05 except for updating Fred's author > block. I don't expect significant changes in protocol operation and = am > unaware of open feedback in that direction (thus also the > early-allocation request). >=20 > As there haven't been any changes I'm unsure whether I should = re-present > the document; it'd probably end up being a repeat wasting people's = time > but I'd be happy to bring it up... >=20 >=20 > Cheers, >=20 >=20 > -David >=20 > [*] early-allocation seems to not apply for blocks under "Expert = Review" > procedure, not sure if there is a process there? From nobody Tue Oct 18 15:55:52 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D71112947D; Tue, 18 Oct 2016 15:55:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.268 X-Spam-Level: * X-Spam-Status: No, score=1.268 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SORBS_WEB=3.599, RP_MATCHES_RCVD=-0.431] autolearn=no autolearn_force=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 hE5Qx4bjIryG; Tue, 18 Oct 2016 15:55:50 -0700 (PDT) Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 6CDEB129437; Tue, 18 Oct 2016 15:55:50 -0700 (PDT) Received: from tops.chopps.org (eb.guest.johnshopkins.net [192.12.13.1]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 7D04A60B9A; Tue, 18 Oct 2016 22:55:49 +0000 (UTC) User-agent: mu4e 0.9.16; emacs 25.1.1 From: To: "isis-wg\@ietf.org list" Date: Tue, 18 Oct 2016 18:55:48 -0400 Message-ID: <874m49nu6j.fsf@chopps.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Archived-At: Cc: "isis-ads@ietf.org" Subject: [Isis-wg] IS-IS Agenda Slot Request for IETF 97 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 22:55:51 -0000 --=-=-= Content-Type: text/plain Hi Folks, We have a preliminary agenda slot for the upcoming IETF 97. It is a 1 hour slot on Wednesday November 16th from 11:10 to 12:10. Please submit any requests for a slot to Thanks, Chris & Hannes. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJYBqh0AAoJEC4dgw7XuDAlkLUQAINLPUrFzPtJXfF9knUGoiX4 PCFZbNSezpBRl1AVCl0CE2z3Bjt8SEVlGB2QR8xXLB7eiiFP9+zI6uiY+gBPu7cb o/Hg4k1TlC4hRRQ/uDd7xIZm9d8WCCAtlGRDthFCNhBCqgmKP9Mk5QcMg2Fa6BQk 07bqEEhdAW5LoJHvBqXaNP92Lz3RUPGBgIguPMI7CBc5GMvgMvb7joeVUCk3+ngF 2EmDnAmapMney2pe958kyUbNL0fC/we6bQxkbhFR9coee5UqEURDBVg1fs5rjtdH kigox6RfHduIJ+OOJ24+taDjOtyVZglBhlQ9u3z4bNV9h+D6tUjd4mfPH6KRcOOY j7wbwZvyoal6MqFyD1zTVCRli9Z6xyMHNcpNluAIh9jIQ3KRmEbHyCWAw24CS/1O 3/MGQ2qGvWGJOzsfqgyxYTWYEi55Inz7YLIn2GKy/ugN1J8wr3CcYS9cbhVBcukb G8WxG80w/DvfmchqXzpGs1NwthbaoMyaiPpknln/O4kq9uoxbZWys7O21KomxFu0 MLAF2CirB882+NQwevwc99wH+aj5qK1nCum4zFGD70mi3RPRLxdforg8AY2dAsAd 7VTSMFhp5DhYtLvyy0WzkStxVXPrBJONFe6lrRUIs5xSEeWqpmTw/kjN+MOidao4 oz6+333MazZQvPI0DOGM =iT3S -----END PGP SIGNATURE----- --=-=-=-- From nobody Wed Oct 19 17:17:32 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 855E812986F; Wed, 19 Oct 2016 17:17:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=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 WdEISv7ASLlX; Wed, 19 Oct 2016 17:17:14 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F5701294AD; Wed, 19 Oct 2016 17:17:00 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 2B228B80155; Wed, 19 Oct 2016 17:17:00 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161020001700.2B228B80155@rfc-editor.org> Date: Wed, 19 Oct 2016 17:17:00 -0700 (PDT) Archived-At: Cc: drafts-update-ref@iana.org, isis-wg@ietf.org, rfc-editor@rfc-editor.org Subject: [Isis-wg] RFC 7981 on IS-IS Extensions for Advertising Router Information X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2016 00:17:24 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7981 Title: IS-IS Extensions for Advertising Router Information Author: L. Ginsberg, S. Previdi, M. Chen Status: Standards Track Stream: IETF Date: October 2016 Mailbox: ginsberg@cisco.com, sprevidi@cisco.com, mach.chen@huawei.com Pages: 10 Characters: 20235 Obsoletes: RFC 4971 I-D Tag: draft-ietf-isis-rfc4971bis-04.txt URL: https://www.rfc-editor.org/info/rfc7981 DOI: http://dx.doi.org/10.17487/RFC7981 This document defines a new optional Intermediate System to Intermediate System (IS-IS) TLV named CAPABILITY, formed of multiple sub-TLVs, which allows a router to announce its capabilities within an IS-IS level or the entire routing domain. This document obsoletes RFC 4971. This document is a product of the IS-IS for IP Internets Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Wed Oct 19 17:17:57 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B36B1129887; Wed, 19 Oct 2016 17:17:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=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 gmCp-AZ8_P6t; Wed, 19 Oct 2016 17:17:38 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C09B12986E; Wed, 19 Oct 2016 17:17:18 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 94777B8015C; Wed, 19 Oct 2016 17:17:18 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161020001718.94777B8015C@rfc-editor.org> Date: Wed, 19 Oct 2016 17:17:18 -0700 (PDT) Archived-At: Cc: drafts-update-ref@iana.org, isis-wg@ietf.org, rfc-editor@rfc-editor.org Subject: [Isis-wg] RFC 7987 on IS-IS Minimum Remaining Lifetime X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2016 00:17:47 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7987 Title: IS-IS Minimum Remaining Lifetime Author: L. Ginsberg, P. Wells, B. Decraene, T. Przygienda, H. Gredler Status: Standards Track Stream: IETF Date: October 2016 Mailbox: ginsberg@cisco.com, pauwells@cisco.com, bruno.decraene@orange.com, prz@juniper.net, hannes@rtbrick.com Pages: 9 Characters: 18295 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-remaining-lifetime-04.txt URL: https://www.rfc-editor.org/info/rfc7987 DOI: http://dx.doi.org/10.17487/RFC7987 Corruption of the Remaining Lifetime field in a Link State Protocol Data Unit (LSP) can go undetected. In certain scenarios, this may cause or exacerbate flooding storms. It is also a possible denial-of-service attack vector. This document defines a backwards-compatible solution to this problem. This document is a product of the IS-IS for IP Internets Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Thu Oct 20 13:44:01 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2EE7129678 for ; Thu, 20 Oct 2016 13:43:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.951 X-Spam-Level: X-Spam-Status: No, score=-14.951 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.431, 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 afinOo6Xq6wY for ; Thu, 20 Oct 2016 13:43:58 -0700 (PDT) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D3511294A4 for ; Thu, 20 Oct 2016 13:43:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12347; q=dns/txt; s=iport; t=1476996238; x=1478205838; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=UxCopG3TaNb9oxXSucLsFSyijAwhxUGSi65uRymfWMA=; b=M4OVIfzC/luphGjBacR83Nq3uAlUZRTyM2HZgtrnoF1qBWgMJ5NSTz8v ZZnIe0M3mq7hbt7GnyU1kfexbv2u4+u6FXI+5KivBx8yz8pXeFhqvOMtq QElNecgdegA5hL22OWieZgK9fenvKxe/aKawK3VOjTi0wLbDRnOmuowQ5 o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CpAQBJKwlY/4sNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgwg2AQEBAQEdV30HjS2WfI8ohRWCCCeFegKBfT8UAQIBAQEBAQEBYii?= =?us-ascii?q?EYgEBAQQtXAIBCA4DBAEBKAcyFAkIAQEEARIIiEoOw1UBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEXBYY9hFWEI1qFKQWaDgGGKYlcgXWEaYkkjH+DfwEeNliDBgMcGYE?= =?us-ascii?q?6coZqgS+BAAEBAQ?= X-IronPort-AV: E=Sophos;i="5.31,372,1473120000"; d="scan'208,217";a="162045116" Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Oct 2016 20:43:57 +0000 Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u9KKhvLg027145 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Oct 2016 20:43:57 GMT Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Oct 2016 15:43:56 -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, 20 Oct 2016 15:43:56 -0500 From: "Les Ginsberg (ginsberg)" To: Chris Bowers , ISIS-WG Thread-Topic: [Isis-wg] removing Controlled Convergence sub-TLV from draft-ietf-isis-mrt-02 Thread-Index: AdIoinEwvgg0c8IhSPibxPBzdXrJowChyCug Date: Thu, 20 Oct 2016 20:43:56 +0000 Message-ID: References: In-Reply-To: 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.154.163.93] Content-Type: multipart/alternative; boundary="_000_b6e1036655a545dc8c39d24f78a9a2c4XCHALN001ciscocom_" MIME-Version: 1.0 Archived-At: Subject: Re: [Isis-wg] removing Controlled Convergence sub-TLV from draft-ietf-isis-mrt-02 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2016 20:44:00 -0000 --_000_b6e1036655a545dc8c39d24f78a9a2c4XCHALN001ciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Chris - draft-bryant-rtgwg-param-sync introduces a new level of hierarchy in IS-IS = by defining a generic "NWP" sub-TLV inside Router Capability TLV and then u= sing a new registry to define sub-sub-TLVs. I fail to see why this is necessary. While it is true that traditional IS-I= S is limited to 255 sub-TLV codepoints for Router Capability TLV, as of to= day we have only used 20+ of those codepoints - so we are in no danger of r= unning out. And sub-sub-TLV encoding becomes less efficient as it requires= 2 extra bytes to encode the sub-sub-TLV wrapper. If your argument is that you intend to use "NWP" for a large number of para= meters then I immediately get concerned about what it is you have in mind t= hat would quickly exhaust the sub-TLV space. Please either drop the sub-sub-TLV proposal or be more transparent as to wh= y you think it is needed. I also note the new proposal does not include MTID associated w the converg= ence parameter - is that change intentional? Les From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Chris Bowers Sent: Monday, October 17, 2016 8:42 AM To: ISIS-WG Subject: [Isis-wg] removing Controlled Convergence sub-TLV from draft-ietf-= isis-mrt-02 ISIS WG, The authors of draft-ietf-isis-mrt-02 are planning to remove the Controlle= d Convergence sub-TLV that draft, and instead use on an equivalent extension being defined in: https://tools.ietf.org/html/draft-bryant-rtgwg-param-sync-00 Since the Controlled Convergence sub-TLV communicates information that may = be useful for applications other that MRT, it makes sense to have it in a separate docume= nt to allow it to be better vetted in the context of those other applications. I don't think that anyone has implemented the Controlled Convergence sub-TL= V in draft-ietf-isis-mrt-02. But if this is not the case, or anyone has another objection to removing it= from draft-ietf-isis-mrt-02, please raise that objection in the next week or so. Thanks, Chris --_000_b6e1036655a545dc8c39d24f78a9a2c4XCHALN001ciscocom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Chris –<= /span>

 <= /p>

draft-bryant-rtgwg-param-= sync introduces a new level of hierarchy in IS-IS by defining a generic = 220;NWP” sub-TLV inside Router Capability TLV and then using a new registry to define sub-sub-TLVs.

I fail to see why this is= necessary. While it is true that traditional IS-IS is limited to 255 sub-T= LV codepoints for Router Capability TLV,  as of today we have only used 20+ of those codepoints – so we are in no danger = of running out.  And sub-sub-TLV encoding becomes less efficient as it= requires 2 extra bytes to encode the sub-sub-TLV wrapper.

 <= /p>

If your argument is that = you intend to use “NWP” for a large number of parameters then I= immediately get concerned about what it is you have in mind that would quickly exhaust the sub-TLV space.

 <= /p>

Please either drop the su= b-sub-TLV proposal or be more transparent as to why you think it is needed.=

 <= /p>

I also note the new propo= sal does not include MTID associated w the convergence parameter – is= that change intentional?

 <= /p>

   Les

 <= /p>

 <= /p>

 <= /p>

From: Isis-wg = [mailto:isis-wg-bounces@ietf.org] On Behalf Of Chris Bowers
Sent: Monday, October 17, 2016 8:42 AM
To: ISIS-WG
Subject: [Isis-wg] removing Controlled Convergence sub-TLV from draf= t-ietf-isis-mrt-02

 

ISIS WG,

 

The authors of draft-ietf-isis-mrt-02&n= bsp; are planning to remove the Controlled Convergence sub-TLV that draft,

and instead use on an equivalent extens= ion being defined in:

 

 

Since the Controlled Convergence sub-TL= V communicates information that may be useful for

applications other that MRT, it makes s= ense to have it in a separate document to allow it to be<= /p>

better vetted in the context of those o= ther applications. 

 

I don’t think that anyone has imp= lemented the Controlled Convergence sub-TLV in draft-ietf-isis-mrt-02. = ;

But if this is not the case, or anyone = has another objection to removing it from draft-ietf-isis-mrt-02, please

raise that objection in the next week o= r so.

 

Thanks,

Chris

 

 

--_000_b6e1036655a545dc8c39d24f78a9a2c4XCHALN001ciscocom_-- From nobody Fri Oct 21 16:22:19 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2058C1296EA; Fri, 21 Oct 2016 16:21:07 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , X-Test-IDTracker: no X-IETF-IDTracker: 6.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147709206712.28214.17862802538415580260.idtracker@ietfa.amsl.com> Date: Fri, 21 Oct 2016 16:21:07 -0700 Archived-At: Cc: isis-wg@ietf.org Subject: [Isis-wg] isis - Requested session has been scheduled for IETF 97 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2016 23:21:07 -0000 Dear Hannes Gredler, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. isis Session 1 (1:30:00) Wednesday, Morning Session II 1110-1210 Room Name: Park Ballroom 1 size: 125 --------------------------------------------- Request Information: --------------------------------------------------------- Working Group Name: IS-IS for IP Internets Area Name: Routing Area Session Requester: Hannes Gredler Number of Sessions: 1 Length of Session(s): 1.5 Hours Number of Attendees: 75 Conflicts to Avoid: First Priority: ospf rtgarea Second Priority: rtgwg spring Third Priority: trill netmod idr Special Requests: Alia has suggested that we do a joint-session between ospf and isisat IETF97. so please rather than avoiding a conflict with ospf, schedule a back to back joint meeting. - thanks ! --------------------------------------------------------- From nobody Mon Oct 24 01:52:03 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E6DF129646 for ; Mon, 24 Oct 2016 01:52:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.331 X-Spam-Level: X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] autolearn=ham autolearn_force=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 0tVtBygsL6Js for ; Mon, 24 Oct 2016 01:52:01 -0700 (PDT) Received: from gilfert.gredler.at (gilfert.gredler.at [87.106.222.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 426D0129640 for ; Mon, 24 Oct 2016 01:52:01 -0700 (PDT) Received: from hannes-mba.local (188-23-180-232.adsl.highway.telekom.at [::ffff:188.23.180.232]) (AUTH: PLAIN hannes, SSL: TLSv1/SSLv3,128bits,AES128-SHA) by gilfert.gredler.at with ESMTPSA; Mon, 24 Oct 2016 10:51:59 +0200 id 0000000002FAC60F.00000000580DCBAF.000030E9 To: "isis-wg@ietf.org" From: Hannes Gredler Message-ID: <94e487a2-0c42-cd36-1e2c-b892813062a5@gredler.at> Date: Mon, 24 Oct 2016 10:51:54 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Cc: Christian Hopps Subject: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 08:52:02 -0000 WG, the authors of draft-ietf-isis-mi-bis-00 have asked for a WGLC. please provide feedback/concerns/suggested amendments within 2 weeks. thanks, /hannes & chris From nobody Mon Oct 24 02:06:57 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37CDC129436 for ; Mon, 24 Oct 2016 02:06:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.331 X-Spam-Level: X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] autolearn=ham autolearn_force=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 tmBLOf9fVo4H for ; Mon, 24 Oct 2016 02:06:52 -0700 (PDT) Received: from gilfert.gredler.at (gilfert.gredler.at [87.106.222.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AC531293F9 for ; Mon, 24 Oct 2016 02:06:51 -0700 (PDT) Received: from hannes-mba.local (188-23-180-232.adsl.highway.telekom.at [::ffff:188.23.180.232]) (AUTH: PLAIN hannes, SSL: TLSv1/SSLv3,128bits,AES128-SHA) by gilfert.gredler.at with ESMTPSA; Mon, 24 Oct 2016 11:06:50 +0200 id 0000000002FAC695.00000000580DCF2A.00003142 To: "isis-wg@ietf.org" From: Hannes Gredler Message-ID: <0a3ccd4c-342b-3f4d-39dc-79c38d657f78@gredler.at> Date: Mon, 24 Oct 2016 11:06:46 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Cc: Christian Hopps Subject: [Isis-wg] WG adoption for draft-tantsura-isis-segment-routing-msd X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 09:06:56 -0000 WG, the authors of draft-tantsura-isis-segment-routing-msd have requested adoption as a WG item. https://datatracker.ietf.org/doc/draft-tantsura-isis-segment-routing-msd/ opinions/comments appreciated. thanks, /hannes & chris From nobody Mon Oct 24 02:07:53 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D52E12943F; Mon, 24 Oct 2016 02:07:52 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: , , X-Test-IDTracker: no X-IETF-IDTracker: 6.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147730007264.15547.12657896955728217634.idtracker@ietfa.amsl.com> Date: Mon, 24 Oct 2016 02:07:52 -0700 Archived-At: Subject: [Isis-wg] The ISIS WG has placed draft-tantsura-isis-segment-routing-msd in state "Call For Adoption By WG Issued" X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 09:07:52 -0000 The ISIS WG has placed draft-tantsura-isis-segment-routing-msd in state Call For Adoption By WG Issued (entered by Hannes Gredler) The document is available at https://datatracker.ietf.org/doc/draft-tantsura-isis-segment-routing-msd/ From nobody Mon Oct 24 02:15:43 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB191294C8; Mon, 24 Oct 2016 02:15:42 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: , , X-Test-IDTracker: no X-IETF-IDTracker: 6.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147730054213.15507.2940639919835305238.idtracker@ietfa.amsl.com> Date: Mon, 24 Oct 2016 02:15:42 -0700 Archived-At: Subject: [Isis-wg] The ISIS WG has placed draft-xu-isis-encapsulation-cap in state "Adopted by a WG" X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 09:15:42 -0000 The ISIS WG has placed draft-xu-isis-encapsulation-cap in state Adopted by a WG (entered by Hannes Gredler) The document is available at https://datatracker.ietf.org/doc/draft-xu-isis-encapsulation-cap/ Comment: good quality discussion on-list in february/march timeframe. From nobody Mon Oct 24 02:21:51 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE42D1295A4 for ; Mon, 24 Oct 2016 02:21:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.331 X-Spam-Level: X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] autolearn=ham autolearn_force=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 JSQ36PT_NPSo for ; Mon, 24 Oct 2016 02:21:48 -0700 (PDT) Received: from gilfert.gredler.at (gilfert.gredler.at [87.106.222.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AB5312943D for ; Mon, 24 Oct 2016 02:21:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) (uid 1000) by gilfert.gredler.at with local; Mon, 24 Oct 2016 11:21:46 +0200 id 0000000002FAC667.00000000580DD2AA.0000320C Date: Mon, 24 Oct 2016 11:21:46 +0200 From: Hannes Gredler To: uma.chunduri@gmail.com Message-ID: <20161024092146.GA12580@gredler.at> References: <1B502206DFA0C544B7A604691520086358001538@eusaamb106.ericsson.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <1B502206DFA0C544B7A604691520086358001538@eusaamb106.ericsson.se> User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: Cc: Christian Hopps , isis-wg@ietf.org Subject: Re: [Isis-wg] WG adoption of draft-xu-isis-encapsulation-cap X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 09:21:51 -0000 uma, guess we have rough consensus that this is work that the WG wants to take on - please resubmit as draft-ietf-isis-encapsulation-cap. thanks ! /hannes & chris On Fri, Apr 08, 2016 at 03:24:40AM +0000, Uma Chunduri wrote: | Les, | | Thx for your reply. | | > Some of us have suggested that there are existing mechanisms which will serve just as well - if not better. | | What existing mechanism do we have to advertise the tunnel capabilities and the associated parameters of the egress node to be used at an ingress node?? | | I think w.r.t tags usage - | | Multiple responses was given in the mailing list including http://www.ietf.org/mail-archive/web/isis-wg/current/msg04500.html | http://www.ietf.org/mail-archive/web/isis-wg/current/msg04519.html | | However we can further update the draft to include provisioning requirements at ingress node with available options for the operators to exercise the preference. | (it seems per offline discussion @ietf95). | | -- | Uma C. | | | -----Original Message----- | From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Les Ginsberg (ginsberg) | Sent: Thursday, March 10, 2016 7:41 AM | To: Philip Christian; isis-wg@ietf.org; xuxiaohu@huawei.com | Subject: [Isis-wg] Relationship between draft-xu-isis-encapsulation-cap and draft-ietf-isis-auto-encap-03 | | (Subject was " Re: [Isis-wg] WG Adoption Call for draft-xu-isis-encapsulation-cap") | | (I have deliberately changed the subject and removed (most of) the original thread.) | | Philip/Xiaohu - | | For me the debate about whether the same codepoint should be used in the two drafts serves neither constituency. | | The two drafts are trying to address two qualitatively different issues. | | In the case of draft-xu-isis-encapsulation-cap the authors are suggesting that explicitly advertising supported tunnel encaps/endpoints is useful in order to support partial deployment of some existing encap (MPLS, SR) over a common L3 layer or to support some form of traffic engineering (RLFA example is cited). The debate going on is NOT about the encoding of the advertisement, it is about whether the advertisement is needed at all. Some of us have suggested that there are existing mechanisms which will serve just as well - if not better. | | In the case of draft-ietf-isis-auto-encap-03, the draft is trying to address the case of islands where a common network layer is not supported (notably an IP island in a CLNS network - or vice versa) - in which case forwarding is not possible at all without introducing some tunneling encap. The debate (if memory serves...it has been 12 years :-) ) was about whether this is a problem which needs solving. For the SONET deployment community this issue did exist (not sure whether it still does) - but from the IP/IPv6 community the need for solving this problem was not perceived as great. | | I think Philip has a point that it could be possible to use the codepoint from the auto-encap draft in support of draft-xu-isis-encapsulation-cap - but focusing on that debate when the need for draft-xu-isis-encapsulation-cap is still being debated seems at best premature. | | I also think that using draft-xu-isis-encapsulation-cap to try to advance draft-ietf-isis-auto-encap-03 is inappropriate. The need to support the use case defined in the auto-encap draft should be discussed on its own merits. It was discussed years ago - whether it needs to be revived should be the subject of a separate thread (if at all). I am concerned that there might be a codepoint in use which is not documented in the IANA registry - so it would be useful to hear whether this technology is in active use in SONET deployments. The draft itself states this is a migration tool - if the migration has already occurred then obviously this makes reviving auto-encap moot. | | Les | | | > -----Original Message----- | > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Philip | > Christian | > Sent: Monday, February 29, 2016 3:30 AM | > To: isis-wg@ietf.org | > Subject: Re: [Isis-wg] WG Adoption Call for | > draft-xu-isis-encapsulation-cap | > | > Please can people explain how | > | > https://datatracker.ietf.org/doc/draft-xu-isis-encapsulation-cap/ | > | > might fit in with, or cause problems with this | > | > https://tools.ietf.org/html/draft-ietf-isis-auto-encap-03 | > | > which was adopted by the ITU-T and appears to be still very much part | > of IT-T G.7712. | _______________________________________________ | Isis-wg mailing list | Isis-wg@ietf.org | https://www.ietf.org/mailman/listinfo/isis-wg | | _______________________________________________ | Isis-wg mailing list | Isis-wg@ietf.org | https://www.ietf.org/mailman/listinfo/isis-wg From nobody Mon Oct 24 02:31:39 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3966B129513; Mon, 24 Oct 2016 02:31:38 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: , , X-Test-IDTracker: no X-IETF-IDTracker: 6.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147730149823.15463.9829258640428193290.idtracker@ietfa.amsl.com> Date: Mon, 24 Oct 2016 02:31:38 -0700 Archived-At: Subject: [Isis-wg] The ISIS WG has placed draft-baker-ipv6-isis-dst-src-routing in state "Call For Adoption By WG Issued" X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 09:31:38 -0000 The ISIS WG has placed draft-baker-ipv6-isis-dst-src-routing in state Call For Adoption By WG Issued (entered by Hannes Gredler) The document is available at https://datatracker.ietf.org/doc/draft-baker-ipv6-isis-dst-src-routing/ Comment: David Lamparter asked for adoption on 18-Oct-2016 From nobody Mon Oct 24 04:25:33 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9997F12948A; Mon, 24 Oct 2016 04:25:29 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147730832959.15451.9032060055103061689.idtracker@ietfa.amsl.com> Date: Mon, 24 Oct 2016 04:25:29 -0700 Archived-At: Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D Action: draft-ietf-isis-encapsulation-cap-00.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 11:25:29 -0000 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 of the IETF. Title : Advertising Tunnelling Capability in IS-IS Authors : Xiaohu Xu Bruno Decraene Robert Raszuk Uma Chunduri Luis M. Contreras Luay Jalil Filename : draft-ietf-isis-encapsulation-cap-00.txt Pages : 11 Date : 2016-10-24 Abstract: Some networks use tunnels for a variety of reasons. A large variety of tunnel types are defined and the ingress needs to select a type of tunnel which is supported by the egress. This document defines how to advertise egress tunnel capabilities in IS-IS Router Capability TLV. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-isis-encapsulation-cap/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-isis-encapsulation-cap-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Oct 24 06:31:23 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B657E1295F3 for ; Mon, 24 Oct 2016 06:31:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.952 X-Spam-Level: X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 GRnVC4qN5aWu for ; Mon, 24 Oct 2016 06:31:19 -0700 (PDT) Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5320A129616 for ; Mon, 24 Oct 2016 06:31:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=721; q=dns/txt; s=iport; t=1477315879; x=1478525479; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=wNESGC3uNNseNorAmLes4ND2WbpQ7bnUkNW+Zj8/Ktk=; b=RLg5kIxDZFicfs7e9v7IXXzs/IKj07/TO60m1YDmdkyXKzpW0HJFSCDi nEukRGVNxMHKr4izXBGoG4+GpFrmt5JE/rJpXURgYw3aDnrhbRJek0OOT cMmyVGyElk8aZ82gpXpV8djRieUv2Ij+10cCT7D/wOQM1s58Ngc0vICIj Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B6AQD0Cw5Y/5NdJa1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgyoBAQEBAR1YfQeNLZZ7lD+CBxwLhXoCgWI/FAECAQEBAQEBAWIohGI?= =?us-ascii?q?BAQEEAQEBNzQLDAQCAQgRBAEBHwkHJwsUCQgCBAENBQiISg7BeQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBARcFhj2EVYomAQSaFAGQC4F1hG2JJ40GhAABHjZehQJyh0G?= =?us-ascii?q?BAAEBAQ?= X-IronPort-AV: E=Sophos;i="5.31,542,1473120000"; d="scan'208";a="338030374" Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Oct 2016 13:31:18 +0000 Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u9ODVIrg025836 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 24 Oct 2016 13:31:18 GMT Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 24 Oct 2016 08:31:17 -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; Mon, 24 Oct 2016 08:31:17 -0500 From: "Les Ginsberg (ginsberg)" To: Hannes Gredler , "isis-wg@ietf.org" Thread-Topic: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt Thread-Index: AQHSLdPoq0KOsWIqd0C1+KyvjAjbTaC3mTzQ Date: Mon, 24 Oct 2016 13:31:17 +0000 Message-ID: <3195322f5e7f41739d3bccd52c14a987@XCH-ALN-001.cisco.com> References: <94e487a2-0c42-cd36-1e2c-b892813062a5@gredler.at> In-Reply-To: <94e487a2-0c42-cd36-1e2c-b892813062a5@gredler.at> 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.24.105.126] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: Christian Hopps Subject: Re: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 13:31:22 -0000 Support as co-author. I am not aware of any IPR relevant to this draft. Les > -----Original Message----- > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Hannes > Gredler > Sent: Monday, October 24, 2016 1:52 AM > To: isis-wg@ietf.org > Cc: Christian Hopps > Subject: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt >=20 > WG, >=20 >=20 > the authors of draft-ietf-isis-mi-bis-00 have asked for a WGLC. >=20 >=20 > please provide feedback/concerns/suggested amendments within 2 weeks. >=20 > thanks, >=20 > /hannes & chris >=20 > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg From nobody Mon Oct 24 06:53:54 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51FC2129713 for ; Mon, 24 Oct 2016 06:53:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.952 X-Spam-Level: X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 cADY_wkBkJTp for ; Mon, 24 Oct 2016 06:53:51 -0700 (PDT) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14A341297C1 for ; Mon, 24 Oct 2016 06:53:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=862; q=dns/txt; s=iport; t=1477317230; x=1478526830; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=fc/iIi2Vxc3TXUYale6t5oNAxP2jHMYY00u3ZSot728=; b=MHzpuPtiL6hDIQGQp7BdrrH8XU6wZ1tUUfAGRirkhN7pIXKPTCQgrz00 fx3REbajVQvqBkJMuKZZoUiu1b1Tm2+wJ04xDc7XuXCJhUIxyYZ0zF5Vv LafHJznwDIenCHKYpkrQjRC1TJ61ur43YOI+ggazGaMdofHPMmmnXQMte 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B6AQBiEQ5Y/4oNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgyoBAQEBAR1YfQeNLZZ7lD+CBxwNhXgCgWI/FAECAQEBAQEBAWIohGI?= =?us-ascii?q?BAQEEAQEBNzQLDAQCAQgRBAEBHwkHJwsUCQgCBAENBQiISg7BdwEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBARcFhj2EVYomBZoUAYYpiWKBdYgnhW2NBoQAAR42XoUCcod?= =?us-ascii?q?BgQABAQE?= X-IronPort-AV: E=Sophos;i="5.31,542,1473120000"; d="scan'208";a="339474236" Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Oct 2016 13:53:49 +0000 Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u9ODrnm2022935 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 24 Oct 2016 13:53:49 GMT Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 24 Oct 2016 08:53:48 -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; Mon, 24 Oct 2016 08:53:48 -0500 From: "Les Ginsberg (ginsberg)" To: Hannes Gredler , "isis-wg@ietf.org" Thread-Topic: [Isis-wg] WG adoption for draft-tantsura-isis-segment-routing-msd Thread-Index: AQHSLdX+SH7wmCh6pE+HvgxDb217cKC3oBRw Date: Mon, 24 Oct 2016 13:53:48 +0000 Message-ID: <0396e90df94544178321fcd3605e9158@XCH-ALN-001.cisco.com> References: <0a3ccd4c-342b-3f4d-39dc-79c38d657f78@gredler.at> In-Reply-To: <0a3ccd4c-342b-3f4d-39dc-79c38d657f78@gredler.at> 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.24.105.126] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: Christian Hopps Subject: Re: [Isis-wg] WG adoption for draft-tantsura-isis-segment-routing-msd X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 13:53:52 -0000 I have read the draft and believe the simple protocol extension advertises = information which is useful. I support WG adoption. Les > -----Original Message----- > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Hannes > Gredler > Sent: Monday, October 24, 2016 2:07 AM > To: isis-wg@ietf.org > Cc: Christian Hopps > Subject: [Isis-wg] WG adoption for draft-tantsura-isis-segment-routing-ms= d >=20 > WG, >=20 > the authors of draft-tantsura-isis-segment-routing-msd have requested > adoption as a WG item. >=20 > https://datatracker.ietf.org/doc/draft-tantsura-isis-segment-routing-msd/ >=20 > opinions/comments appreciated. >=20 > thanks, >=20 > /hannes & chris >=20 > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg From nobody Mon Oct 24 07:40:30 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 048101296DA for ; Mon, 24 Oct 2016 07:40:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 BJGzSSZy5l6a for ; Mon, 24 Oct 2016 07:40:25 -0700 (PDT) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31F71129458 for ; Mon, 24 Oct 2016 07:40:21 -0700 (PDT) Received: by mail-qk0-x231.google.com with SMTP id i68so856477qke.7 for ; Mon, 24 Oct 2016 07:40:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zI6slnnn+09UNKwnMDfa3ml8E71goW/XZXoUFbrZiHY=; b=dOxzLfuj5W8QGYCojzDiLcjapd3sWv6Ysm3nqbgMlUIyDpgpjZ0vjnjoIq+mZ3tkTP ibGG4fs+JSIZ4ZGJLtYx8F1REvPBr90rIAKAIql1pPpN3VTQx2jdYwzTkUmWlV7kkxka YjbfSGoKBOQsq/8TrQqfYNuDJxNGP/eNRPPc7cAUpRWE9GWuuVwxYati0eeXcocQyNr8 JgJDoQLJjOMnlMOi/ZZsH9pn9TQhIchGtfGYWXtopRbOgIHHAqGOlzx/uwGU237PPwCf TXugec+4FGxhGfIpAdTtbXNIgSHqZ3qZhbBAxr5a6ybxAOS088drwQ2zqgdUJ7jtMcSh wZEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zI6slnnn+09UNKwnMDfa3ml8E71goW/XZXoUFbrZiHY=; b=e77s+rtAqatVvvS1qdCH6pxZDH5KinbBfrqfqXW8aW6arD+2UW1R66xAOfhbIhcIWk hNXPReq90tet9Kuo2CvpaesqUukRDm2TVn/AFcSQla1EXsu4JcCCN0923pDFblkSoG/h 7oMXh2qyh2Kgus3jp+ntOuqXDurgTYsMeiYeDcSv314glRNbnP/IBfLvTNxHp5/DKtr3 Q0Fo89JeNZNb2kfSZ/WIUqJtaTB+sK68tSLQPS7M51goCVoiFCm22BeftYTC5sQR5k7r SMKub5FBsQHtPz6sF1fY0WQgI9X/4hjCWw+ijPcO9GfyhHImyCfkjwn6410740VRoaZP Y2iw== X-Gm-Message-State: ABUngvePfGQwzJ4L/13aFkOnaXdRdPeSkbeTyV85PI98FGYq9tKKLDh8Ezl4eUCI9S+t5E+zDrPnVsxOc6HEhw== X-Received: by 10.55.18.7 with SMTP id c7mr16698982qkh.246.1477320020331; Mon, 24 Oct 2016 07:40:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.198.80 with HTTP; Mon, 24 Oct 2016 07:40:19 -0700 (PDT) In-Reply-To: <0a3ccd4c-342b-3f4d-39dc-79c38d657f78@gredler.at> References: <0a3ccd4c-342b-3f4d-39dc-79c38d657f78@gredler.at> From: Mohan Nanduri Date: Mon, 24 Oct 2016 10:40:19 -0400 Message-ID: To: Hannes Gredler Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: Christian Hopps , "isis-wg@ietf.org" Subject: Re: [Isis-wg] WG adoption for draft-tantsura-isis-segment-routing-msd X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 14:40:30 -0000 I support this for WG adoption, this is useful. Cheers, -Mohan On Mon, Oct 24, 2016 at 5:06 AM, Hannes Gredler wrote: > WG, > > the authors of draft-tantsura-isis-segment-routing-msd have requested > adoption as a WG item. > > https://datatracker.ietf.org/doc/draft-tantsura-isis-segment-routing-msd/ > > opinions/comments appreciated. > > thanks, > > /hannes & chris > > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg From nobody Mon Oct 24 07:45:02 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA80F129547 for ; Mon, 24 Oct 2016 07:45:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 IIQ0ie9CyBdo for ; Mon, 24 Oct 2016 07:44:59 -0700 (PDT) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D922C129515 for ; Mon, 24 Oct 2016 07:44:58 -0700 (PDT) Received: by mail-yw0-x232.google.com with SMTP id w3so189291089ywg.1 for ; Mon, 24 Oct 2016 07:44:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9dGRYgN+FEtzXj/EFs0ZwvjFQgTdDE5F/O9sHcY9i7Y=; b=b9yMWC1JPAU13yuo8Cot8gHeJd4+RDiL6NsDSobmm7rqWMAj1tcU+tYyxmwVescFxg kURjY62joEKNP9u7j6H5lJ9qATVfwZtFMbMVoShNEHEIb89jX4HKLzwV0JsOERI4SP2y P4s+I+1sJZCzwChL/am4DNAkTW+8RFm+XLS7ElavMV6rUCux1OWtnuWg6ZMRWdaS63Gn UdpqhumZHLVpmW5SEeFwPveOv0B02+yfHPEEDMUTv0UsHZhB5cbn9sAVt8V6mU74NHjc AMF+IJDUNIsUh2geDoA6A6dIY0RNDAoVU/kruZp2YhDghfWLT9GB1RtF+tvTG4XH2eKX CzEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9dGRYgN+FEtzXj/EFs0ZwvjFQgTdDE5F/O9sHcY9i7Y=; b=apsKI20sCQfTby2Vkn3B8GntCLoXaVcPPz6k6AArUh1Uz+RxAUX4qIa5Yhpa+RXN07 iPtCIW9mdPACAEtegR8MzURVfUFLBd6IX87+KQTv0d4f1JS5D62TU6VsZVImPxhCpPIe TZMEiiWOyMHLxTd1bLJthcdsLqRWo76rf+tl5a6ikj/kaZfRUlI1m//ARX/Ucpzo4ESu d7aWwJqA5gXLh7U9DAtoJZpZsmezr1O0Ye7semvrx8OkzkWWnQGYERIerJCRcQnmwTQf 6RJeDql82bHHxmgnooOnEi4/Sqa8yTh6Jf5owig1cwpf2x2GkExjp1ez/SlGewwk3Qnx m44g== X-Gm-Message-State: ABUngveKQzObVNfLiHgp/rb/ejNBADii1Fiw9eGM6Kv38yt9I670tQtmVdnVP6aQ9aJ6Bj+2x8GtLmxbe5remw== X-Received: by 10.107.36.144 with SMTP id k138mr12136065iok.201.1477320298046; Mon, 24 Oct 2016 07:44:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.6.214 with HTTP; Mon, 24 Oct 2016 07:44:17 -0700 (PDT) In-Reply-To: <0396e90df94544178321fcd3605e9158@XCH-ALN-001.cisco.com> References: <0a3ccd4c-342b-3f4d-39dc-79c38d657f78@gredler.at> <0396e90df94544178321fcd3605e9158@XCH-ALN-001.cisco.com> From: Tony Przygienda Date: Mon, 24 Oct 2016 07:44:17 -0700 Message-ID: To: "Les Ginsberg (ginsberg)" Content-Type: multipart/alternative; boundary=001a11402d1095aa83053f9d6f18 Archived-At: Cc: Christian Hopps , "isis-wg@ietf.org" Subject: Re: [Isis-wg] WG adoption for draft-tantsura-isis-segment-routing-msd X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 14:45:00 -0000 --001a11402d1095aa83053f9d6f18 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable agree with Les ... tony On Mon, Oct 24, 2016 at 6:53 AM, Les Ginsberg (ginsberg) wrote: > I have read the draft and believe the simple protocol extension advertise= s > information which is useful. > I support WG adoption. > > Les > > > > -----Original Message----- > > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Hannes > > Gredler > > Sent: Monday, October 24, 2016 2:07 AM > > To: isis-wg@ietf.org > > Cc: Christian Hopps > > Subject: [Isis-wg] WG adoption for draft-tantsura-isis-segment- > routing-msd > > > > WG, > > > > the authors of draft-tantsura-isis-segment-routing-msd have requested > > adoption as a WG item. > > > > https://datatracker.ietf.org/doc/draft-tantsura-isis- > segment-routing-msd/ > > > > opinions/comments appreciated. > > > > thanks, > > > > /hannes & chris > > > > _______________________________________________ > > Isis-wg mailing list > > Isis-wg@ietf.org > > https://www.ietf.org/mailman/listinfo/isis-wg > > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg > --=20 *We=E2=80=99ve heard that a million monkeys at a million keyboards could pr= oduce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true.* =E2=80=94Robert Wilensky --001a11402d1095aa83053f9d6f18 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
agree with Les ... tony=C2=A0

On Mon, Oct 24, 2016 at 6:53 AM, Les Gin= sberg (ginsberg) <ginsberg@cisco.com> wrote:
I have read the draft and believe the simple protocol e= xtension advertises information which is useful.
I support WG adoption.

=C2=A0 =C2=A0 Les


> -----Original Message-----
> From: Isis-wg [mailto:isis= -wg-bounces@ietf.org] On Behalf Of Hannes
> Gredler
> Sent: Monday, October 24, 2016 2:07 AM
> To: isis-wg@ietf.org
> Cc: Christian Hopps
> Subject: [Isis-wg] WG adoption for draft-tantsura-isis-segment-ro= uting-msd
>
> WG,
>
> the authors of draft-tantsura-isis-segment-routing-msd have reque= sted
> adoption as a WG item.
>
> https://datatracker.ie= tf.org/doc/draft-tantsura-isis-segment-routing-msd/
>
> opinions/comments appreciated.
>
> thanks,
>
> /hannes & chris
>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg=

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www.ietf.org/mailman/listinfo/isis-wg<= br>



--
=
We=E2=80=99ve heard that a million monkeys at a million ke= yboards could produce the complete works of Shakespeare; now, thanks to the= Internet, we know that is not true.
=E2=80=94Robert Wilensky
--001a11402d1095aa83053f9d6f18-- From nobody Mon Oct 24 07:53:04 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A1E012975C for ; Mon, 24 Oct 2016 07:53:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.953 X-Spam-Level: X-Spam-Status: No, score=-14.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 Pof3oXwAbwf1 for ; Mon, 24 Oct 2016 07:53:01 -0700 (PDT) Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF45B12958B for ; Mon, 24 Oct 2016 07:53:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=694; q=dns/txt; s=iport; t=1477320781; x=1478530381; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=QnQuXy3+T2bL2PksiLwwOGls39l6+UXmO4sQBudXHYg=; b=YgC5NPzARppgMPeNMQMXdVSY7YXg8b1CT2axYrjz7cSAVKJtKNahYDfC 29OJxi8vAZRfEyafmKfJB7BMYwzcxvtwbIzT/7HUi7KNH9DJdOEcTo3dp wCVQhUWt6BOaVNJi6FDfLQpvKXJ2Rc+JfMhD9iTYbFcCyXW52jf0tnv0/ 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BtAQDjHw5Y/5pdJa1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgyoBAQEBAR1YfQeNLas7ggccC4V6AhqBST8UAQIBAQEBAQEBYiiEYwE?= =?us-ascii?q?BBAEBASAROgsQAgEIGgImAgICJQsVEAIEAQ0FiFIOtGOMZQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBARcFgQeKC4RHgwSCWwEEmhQBkBKBWBaEbYknkQYBHjZehQJyh0G?= =?us-ascii?q?BAAEBAQ?= X-IronPort-AV: E=Sophos;i="5.31,542,1473120000"; d="scan'208";a="339626126" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Oct 2016 14:53:00 +0000 Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u9OEr0YA026287 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 24 Oct 2016 14:53:00 GMT Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 24 Oct 2016 10:52:59 -0400 Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Mon, 24 Oct 2016 10:52:59 -0400 From: "Acee Lindem (acee)" To: Hannes Gredler , "isis-wg@ietf.org" Thread-Topic: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt Thread-Index: AQHSLdPoReoyVeQ0yUWAqR2bLfF9LqC3sPKA Date: Mon, 24 Oct 2016 14:52:59 +0000 Message-ID: References: <94e487a2-0c42-cd36-1e2c-b892813062a5@gredler.at> In-Reply-To: <94e487a2-0c42-cd36-1e2c-b892813062a5@gredler.at> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.116.152.200] Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: Cc: Christian Hopps Subject: Re: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 14:53:03 -0000 SSBzdXBwb3J0IFdHIGFkb3B0aW9uLg0KVGhhbmtzLA0KQWNlZSANCg0KT24gMTAvMjQvMTYsIDQ6 NTEgQU0sICJJc2lzLXdnIG9uIGJlaGFsZiBvZiBIYW5uZXMgR3JlZGxlciINCjxpc2lzLXdnLWJv dW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIGhhbm5lc0BncmVkbGVyLmF0PiB3cm90ZToNCg0K PldHLA0KPg0KPg0KPnRoZSBhdXRob3JzIG9mIGRyYWZ0LWlldGYtaXNpcy1taS1iaXMtMDAgaGF2 ZSBhc2tlZCBmb3IgYSBXR0xDLg0KPg0KPg0KPnBsZWFzZSBwcm92aWRlIGZlZWRiYWNrL2NvbmNl cm5zL3N1Z2dlc3RlZCBhbWVuZG1lbnRzIHdpdGhpbiAyIHdlZWtzLg0KPg0KPnRoYW5rcywNCj4N Cj4vaGFubmVzICYgY2hyaXMNCj4NCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXw0KPklzaXMtd2cgbWFpbGluZyBsaXN0DQo+SXNpcy13Z0BpZXRmLm9yZw0K Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXNpcy13Zw0KDQo= From nobody Mon Oct 24 08:02:42 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8DEC12956E for ; Mon, 24 Oct 2016 08:02:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.349 X-Spam-Level: X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_DUL=0.001, RP_MATCHES_RCVD=-0.431, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=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 Pue45gaQZh2o for ; Mon, 24 Oct 2016 08:02:35 -0700 (PDT) Received: from relais-inet.orange.com (relais-aub40.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2268E1295C7 for ; Mon, 24 Oct 2016 08:02:27 -0700 (PDT) Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 578641C00D5; Mon, 24 Oct 2016 17:02:25 +0200 (CEST) Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.42]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 341F4180065; Mon, 24 Oct 2016 17:02:25 +0200 (CEST) Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM41.corporate.adroot.infra.ftgroup ([fe80::c845:f762:8997:ec86%19]) with mapi id 14.03.0319.002; Mon, 24 Oct 2016 17:02:25 +0200 From: To: "Les Ginsberg (ginsberg)" , Hannes Gredler , "isis-wg@ietf.org" Thread-Topic: [Isis-wg] WG adoption for draft-tantsura-isis-segment-routing-msd Thread-Index: AQHSLf4RDlUO8eUKSUuD/1Sby5ilyKC3sz4Q Date: Mon, 24 Oct 2016 15:02:24 +0000 Message-ID: <15390_1477321345_580E2281_15390_2391_1_9E32478DFA9976438E7A22F69B08FF921DB3597B@OPEXCLILMA4.corporate.adroot.infra.ftgroup> References: <0a3ccd4c-342b-3f4d-39dc-79c38d657f78@gredler.at> <0396e90df94544178321fcd3605e9158@XCH-ALN-001.cisco.com> In-Reply-To: <0396e90df94544178321fcd3605e9158@XCH-ALN-001.cisco.com> Accept-Language: fr-FR, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.1] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: Christian Hopps Subject: Re: [Isis-wg] WG adoption for draft-tantsura-isis-segment-routing-msd X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 15:02:40 -0000 +1 -----Original Message----- From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Les Ginsberg (= ginsberg) Sent: Monday, October 24, 2016 15:54 To: Hannes Gredler; isis-wg@ietf.org Cc: Christian Hopps Subject: Re: [Isis-wg] WG adoption for draft-tantsura-isis-segment-routing-= msd I have read the draft and believe the simple protocol extension advertises = information which is useful. I support WG adoption. Les > -----Original Message----- > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Hannes=20 > Gredler > Sent: Monday, October 24, 2016 2:07 AM > To: isis-wg@ietf.org > Cc: Christian Hopps > Subject: [Isis-wg] WG adoption for=20 > draft-tantsura-isis-segment-routing-msd >=20 > WG, >=20 > the authors of draft-tantsura-isis-segment-routing-msd have requested=20 > adoption as a WG item. >=20 > https://datatracker.ietf.org/doc/draft-tantsura-isis-segment-routing-m > sd/ >=20 > opinions/comments appreciated. >=20 > thanks, >=20 > /hannes & chris >=20 > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www.ietf.org/mailman/listinfo/isis-wg ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. From nobody Mon Oct 24 10:52:36 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E037612987B; Mon, 24 Oct 2016 10:52:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.952 X-Spam-Level: X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 ZUubdNWsMzIr; Mon, 24 Oct 2016 10:52:34 -0700 (PDT) Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C26A1296DC; Mon, 24 Oct 2016 10:52:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1780; q=dns/txt; s=iport; t=1477331554; x=1478541154; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=CvIh6VwBCupmosEoU+wRAEjoikKTi74pfWv2TpgN+uo=; b=d0rvRkb+53L28gNBMJouhb+OkkmcMAiN8G1giIvZqOWBgoWO79GnYMf8 /895TEjVXPD+5+8Z8B+NaOh+3U+ArkY6jszYSj7tYvUrgvQjUcjVVmyjp 4uUkvvnn8RabQxVBzAdTnoLkc8xFO1wL1c1Mw0XIK5J/NJR+FDmsfgKkb I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BtAQBASQ5Y/4gNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgyoBAQEBAR1YfQeNLas7ggccC4V6AoFnPxQBAgEBAQEBAQFiKIRjAQE?= =?us-ascii?q?EAQEBNzQLEAIBCDYQJwslAgQBDQWIUg7BOQEBAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?RyGPYRViiYFlDeFXQGGKYlpgW5OhB+JJ40GhAABHjZehQJyh0GBAAEBAQ?= X-IronPort-AV: E=Sophos;i="5.31,542,1473120000"; d="scan'208";a="339491154" Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Oct 2016 17:52:33 +0000 Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u9OHqXa2020841 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 24 Oct 2016 17:52:33 GMT Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 24 Oct 2016 12:52:33 -0500 Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Mon, 24 Oct 2016 12:52:32 -0500 From: "Saumya Dikshit (sadikshi)" To: "internet-drafts@ietf.org" , "i-d-announce@ietf.org" Thread-Topic: [Isis-wg] I-D Action: draft-ietf-isis-encapsulation-cap-00.txt Thread-Index: AQHSLelk9Ioz/GBi8kajSqzMvzRax6C4kviA Date: Mon, 24 Oct 2016 17:52:32 +0000 Message-ID: References: <147730832959.15451.9032060055103061689.idtracker@ietfa.amsl.com> In-Reply-To: <147730832959.15451.9032060055103061689.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.6.5.160527 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.65.59.97] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: "isis-wg@ietf.org" Subject: Re: [Isis-wg] I-D Action: draft-ietf-isis-encapsulation-cap-00.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 17:52:36 -0000 I support WG adoption of this publication. Thanks Saumya. On 10/24/16, 4:55 PM, "Isis-wg on behalf of internet-drafts@ietf.org" wrote: > >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 of the IETF. > > Title : Advertising Tunnelling Capability in IS-IS > Authors : Xiaohu Xu > Bruno Decraene > Robert Raszuk > Uma Chunduri > Luis M. Contreras > Luay Jalil > Filename : draft-ietf-isis-encapsulation-cap-00.txt > Pages : 11 > Date : 2016-10-24 > >Abstract: > Some networks use tunnels for a variety of reasons. A large variety > of tunnel types are defined and the ingress needs to select a type of > tunnel which is supported by the egress. This document defines how > to advertise egress tunnel capabilities in IS-IS Router Capability > TLV. > > > >The IETF datatracker status page for this draft is: >https://datatracker.ietf.org/doc/draft-ietf-isis-encapsulation-cap/ > >There's also a htmlized version available at: >https://tools.ietf.org/html/draft-ietf-isis-encapsulation-cap-00 > > >Please note that it may take a couple of minutes from the time of >submission >until the htmlized version and diff are available at tools.ietf.org. > >Internet-Drafts are also available by anonymous FTP at: >ftp://ftp.ietf.org/internet-drafts/ > >_______________________________________________ >Isis-wg mailing list >Isis-wg@ietf.org >https://www.ietf.org/mailman/listinfo/isis-wg From nobody Mon Oct 24 18:18:19 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 785CC129A63 for ; Mon, 24 Oct 2016 18:18:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.652 X-Spam-Level: X-Spam-Status: No, score=-4.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 pkssP7Pl3DWK for ; Mon, 24 Oct 2016 18:18:16 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C18D129A32 for ; Mon, 24 Oct 2016 18:18:15 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CTV43372; Tue, 25 Oct 2016 01:18:14 +0000 (GMT) Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml701-cah.china.huawei.com (10.201.5.93) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 25 Oct 2016 02:18:13 +0100 Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Tue, 25 Oct 2016 09:18:09 +0800 From: Xuxiaohu To: Hannes Gredler , "isis-wg@ietf.org" Thread-Topic: [Isis-wg] WG adoption for draft-tantsura-isis-segment-routing-msd Thread-Index: AQHSLdYGFbSf/VgEk0aQBD+nFGWU5aC4X3xQ Date: Tue, 25 Oct 2016 01:18:09 +0000 Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB24415@NKGEML515-MBX.china.huawei.com> References: <0a3ccd4c-342b-3f4d-39dc-79c38d657f78@gredler.at> In-Reply-To: <0a3ccd4c-342b-3f4d-39dc-79c38d657f78@gredler.at> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.111.184.181] Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.580EB2D6.0192, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 737f627af303d109e99af451ada7a1b4 Archived-At: Cc: Christian Hopps Subject: [Isis-wg] =?gb2312?b?tPC4tDogIFdHIGFkb3B0aW9uIGZvciBkcmFmdC10YW50?= =?gb2312?b?c3VyYS1pc2lzLXNlZ21lbnQtcm91dGluZy1tc2Q=?= X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2016 01:18:18 -0000 SSBoYXZlIHJlYWQgdGhpcyBkcmFmdCBhbmQgc3VwcG9ydCB0aGUgV0cgYWRvcHRpb24gb2YgdGhp cyBkcmFmdC4NCg0KWGlhb2h1DQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ILeivP7IyzogSXNp cy13ZyBbbWFpbHRvOmlzaXMtd2ctYm91bmNlc0BpZXRmLm9yZ10gtPqx7SBIYW5uZXMgR3JlZGxl cg0KPiC3osvNyrG85DogMjAxNsTqMTDUwjI0yNUgMTc6MDcNCj4gytW8/sjLOiBpc2lzLXdnQGll dGYub3JnDQo+ILOty806IENocmlzdGlhbiBIb3Bwcw0KPiDW98ziOiBbSXNpcy13Z10gV0cgYWRv cHRpb24gZm9yIGRyYWZ0LXRhbnRzdXJhLWlzaXMtc2VnbWVudC1yb3V0aW5nLW1zZA0KPiANCj4g V0csDQo+IA0KPiB0aGUgYXV0aG9ycyBvZiBkcmFmdC10YW50c3VyYS1pc2lzLXNlZ21lbnQtcm91 dGluZy1tc2QgaGF2ZSByZXF1ZXN0ZWQgYWRvcHRpb24NCj4gYXMgYSBXRyBpdGVtLg0KPiANCj4g aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtdGFudHN1cmEtaXNpcy1zZWdt ZW50LXJvdXRpbmctbXNkLw0KPiANCj4gb3BpbmlvbnMvY29tbWVudHMgYXBwcmVjaWF0ZWQuDQo+ IA0KPiB0aGFua3MsDQo+IA0KPiAvaGFubmVzICYgY2hyaXMNCj4gDQo+IF9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IElzaXMtd2cgbWFpbGluZyBsaXN0 DQo+IElzaXMtd2dAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0 aW5mby9pc2lzLXdnDQo= From nobody Tue Oct 25 03:20:33 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 266AD1293F9 for ; Tue, 25 Oct 2016 03:20:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.955 X-Spam-Level: X-Spam-Status: No, score=-1.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 mP7trrmhsQvj for ; Tue, 25 Oct 2016 03:20:26 -0700 (PDT) Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7856129463 for ; Tue, 25 Oct 2016 03:20:25 -0700 (PDT) Received: from [37.130.210.2] (helo=doom.twoguys.org) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1byypn-00068m-5c; Tue, 25 Oct 2016 06:19:56 -0400 Received: from doom.twoguys.org (localhost.twoguys.org [127.0.0.1]) by doom.twoguys.org (8.14.4/8.12.11) with ESMTP id u9PAJrx3019034; Tue, 25 Oct 2016 06:19:54 -0400 Received: (from ghankins@localhost) by doom.twoguys.org (8.14.4/8.14.4/Submit) id u9PAJpZM019029; Tue, 25 Oct 2016 06:19:51 -0400 X-Authentication-Warning: doom.twoguys.org: ghankins set sender to greg.hankins@nokia.com using -f Date: Tue, 25 Oct 2016 06:19:51 -0400 From: "Hankins, Greg (Nokia - US)" To: Hannes Gredler Message-ID: <20161025101951.GA18964@nokia.com> References: <94e487a2-0c42-cd36-1e2c-b892813062a5@gredler.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <94e487a2-0c42-cd36-1e2c-b892813062a5@gredler.at> User-Agent: Mutt/1.5.19 (2009-01-05) X-ELNK-Trace: 176464c9115cf5b39c7f779228e2f6aeda0071232e20db4d14f5286651aaa2aa975c787838745ffb350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 37.130.210.2 Archived-At: Cc: Christian Hopps , "isis-wg@ietf.org" Subject: Re: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2016 10:20:30 -0000 I support WGLC. This is needed to for known customer deployment requirements. Greg -- Greg Hankins Senior Product Manager IP/Optical Networks, Nokia -----Original Message----- Date: Mon, 24 Oct 2016 10:51:54 +0200 From: Hannes Gredler To: "isis-wg@ietf.org" Cc: Christian Hopps Subject: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt WG, the authors of draft-ietf-isis-mi-bis-00 have asked for a WGLC. please provide feedback/concerns/suggested amendments within 2 weeks. thanks, /hannes & chris _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www.ietf.org/mailman/listinfo/isis-wg From nobody Wed Oct 26 01:01:24 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 02FF0129A3A; Wed, 26 Oct 2016 01:01:20 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147746888000.18851.13316791630383835755.idtracker@ietfa.amsl.com> Date: Wed, 26 Oct 2016 01:01:20 -0700 Archived-At: Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D Action: draft-ietf-isis-yang-isis-cfg-13.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2016 08:01:20 -0000 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 of the IETF. Title : YANG Data Model for IS-IS protocol Authors : Stephane Litkowski Derek Yeung Acee Lindem Jeffrey Zhang Ladislav Lhotka Filename : draft-ietf-isis-yang-isis-cfg-13.txt Pages : 124 Date : 2016-10-26 Abstract: This document defines a YANG data model that can be used to configure and manage IS-IS protocol on network elements. It also defines an extension module for IS-IS segment routing configuration and operation. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-isis-yang-isis-cfg/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-isis-yang-isis-cfg-13 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-yang-isis-cfg-13 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Oct 26 06:32:56 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5937A129B6C for ; Wed, 26 Oct 2016 06:32:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.331 X-Spam-Level: X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.431] autolearn=ham autolearn_force=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 jv3a5EPgjC-j for ; Wed, 26 Oct 2016 06:32:51 -0700 (PDT) Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id F3D8212941D for ; Wed, 26 Oct 2016 06:32:50 -0700 (PDT) Received: from tops.chopps.org (97-83-46-222.dhcp.trcy.mi.charter.com [97.83.46.222]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 1257C60B5A for ; Wed, 26 Oct 2016 13:32:49 +0000 (UTC) User-agent: mu4e 0.9.16; emacs 25.1.1 From: To: "isis-wg\@ietf.org" Date: Wed, 26 Oct 2016 09:32:49 -0400 Message-ID: <87oa27b5ha.fsf@chopps.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Archived-At: Subject: [Isis-wg] Fwd: [netmod] Delay in publication request of routing-cfg and current -state conventions X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2016 13:32:55 -0000 --=-=-= Content-Type: text/plain Hi Folks, This will clear the way for moving forward with IS-IS (and other routing) yang model(s). Thanks, Chris. Lou Berger writes: > All, > Some may have noticed that there was a bit of a gap between the > close of LC and the submission of the publication request for this > document. While it was gated by a minor update, the more significant > reason for the delay was the consideration of how to proceed with models > that contain the -state branch. > > As we're sure most are aware we have a design team looking at how > datastores might be used to address the applied vs intended config [1] > and the larger "OpState" discussion. There also has been some > discussion on proposals on how to proceed while their work is ongoing, > including a proposal that I promoted - and this model presents the first > opportunity to implement such. > > Based on a fair bit of discussion among the authors, chairs, AD and > design team, we concluded that introducing a new model convention > at this time really doesn't provide any substantive benefit and may in > fact complicate future transition/upgrade approaches. This > consideration is what resulted in the delay. > > The impact of this discussion on routing-cfg is no change. The impact > on -state conventions is that, for now, we (as chairs) feel that models > being submitted for publication request by the WG should follow the > conventions found in RFC7223 and the recommendations documented in > 6087bis section 5.23 [2]. This of course can be change through > discussion in the WG, e.g., based on the output of the DT. > > Lou and Kent > > [1] https://www.ietf.org/mail-archive/web/netmod/current/msg16491.html > [2] https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-08#section-5.23 > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJYELCBAAoJEC4dgw7XuDAlJV0QAKOhbh9pA17XWY2+kizX+u7C wcKepZahWDK9g3MMELjwyiUAc2zAGq9FdImsLq/KKX/TVfwwJQV/dAuA6tq7+zXa sn+FZxSxDQkjkENmWaqRvZqAz1NcoUbG+vqf4ZZDHgsz65hIZoQfcvbUzX7iYZR9 ivrz/AGKEd69RrAPK8zDGw1BAIVyqUXLg/TKrbck+sIDqLO0lPH23NI4tKuiQUEM T4uNcmp6nJXzYp+nX0yC1/SSIt1dFRQ+Nme4US1x/wgt3iRzAfPZ5feX7EsONc7z 6Ay2XtRfCR0j2q6PShHwvDRhCH4dhhtBS4WZuwBOInS4XTysYDZxLcAWhlo2DmSx PNCnneoSwLVQ/uQjnHnCuHZw8/GjrmRxI5l/AYAlp0tV06u+DyCf07Jpm0R4F82H BM0JkDeo1NWWpcrNdQ3VfJwLZUD1dG8TcAYHdlqtsNiTs3RDgCGhbAofei622253 53ab7Rej8h+y4489U4d4tljnVn6qp69km1QsW4dyiHZ7lYOqSw5IdGfTby3x/Sae BqNWXny3zzfbHoUmszSazHyR2DweLFlyHiTnMsOev/KnYfoarYDD8ArCxGXpghUN i/bVseMlzXFEyp8FJZNlfa6VLFDMyipf3BngJItK6nf8oHSOOjfTPO6wrfHMLxod 902nTIA9yefoY8ZkccXc =7biC -----END PGP SIGNATURE----- --=-=-=-- From nobody Wed Oct 26 08:06:11 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A081A129555 for ; Wed, 26 Oct 2016 08:06:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.953 X-Spam-Level: X-Spam-Status: No, score=-14.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 Lf6BbVzpZaPh for ; Wed, 26 Oct 2016 08:06:05 -0700 (PDT) Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3CDD12950F for ; Wed, 26 Oct 2016 08:06:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=716; q=dns/txt; s=iport; t=1477494365; x=1478703965; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ShyD/Z71a8+g30evcRIv45Caoa89zL/IXKWYeCSJRMo=; b=a3kc8FWwpuHW7OMEXz0pCPjvy7ekySN5tqhjZBnh8km+YigkwFt6BHBN 8444+zN9Z47hMMF7HVnd27CSpHeaV+2coczWL6zoubnak1KZEfoqDKHbq MOCwdkWM9jY2WXLCFf22ANgkoOIAYyOW9dE7yoCtyZTDXo26xj2PTEyqR U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AbAQAwxhBY/5xdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyoBAQEBAR1YfQeNLpZ+lD+CCRwLhXsCGoFmPxQBAgEBAQEBAQF?= =?us-ascii?q?iKIRiAQEBAwEBAQEgEToLBQsCAQgYAgImAgICJQsVEAIEDgWITAgOsz6McQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBARcFgQeFNoF9gliER4MELIIvAQSaFgGQH4FYFoR?= =?us-ascii?q?tiSmNCoQAAR42XoUHcoddgQkBAQE?= X-IronPort-AV: E=Sophos;i="5.31,551,1473120000"; d="scan'208";a="167653444" Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Oct 2016 15:05:44 +0000 Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u9QF5iBw008177 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 26 Oct 2016 15:05:44 GMT Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 26 Oct 2016 11:05:43 -0400 Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Wed, 26 Oct 2016 11:05:43 -0400 From: "Stefano Previdi (sprevidi)" To: Hannes Gredler Thread-Topic: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt Thread-Index: AQHSL5psb4h9RmHZuUyvZ71JHRA6pQ== Date: Wed, 26 Oct 2016 15:05:43 +0000 Message-ID: <8746CB9B-F227-4B03-93E9-8688F592CD08@cisco.com> References: <94e487a2-0c42-cd36-1e2c-b892813062a5@gredler.at> In-Reply-To: <94e487a2-0c42-cd36-1e2c-b892813062a5@gredler.at> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.154.160.58] Content-Type: text/plain; charset="utf-8" Content-ID: <11E03D9604E0CE4AA96937911DD6E0D0@emea.cisco.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: Cc: Christian Hopps , "isis-wg@ietf.org" Subject: Re: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2016 15:06:09 -0000 SSBzdXBwb3J0IHRoZSBkcmFmdCBhcyBjby1hdXRob3IgYW5kIEnigJltIG5vdCBhd2FyZSBvZiBh bnkgSVBSIHJlbGF0ZWQgdG8gaXQuDQoNCnMuDQoNCg0KPiBPbiBPY3QgMjQsIDIwMTYsIGF0IDEw OjUxIEFNLCBIYW5uZXMgR3JlZGxlciA8aGFubmVzQGdyZWRsZXIuYXQ+IHdyb3RlOg0KPiANCj4g V0csDQo+IA0KPiANCj4gdGhlIGF1dGhvcnMgb2YgZHJhZnQtaWV0Zi1pc2lzLW1pLWJpcy0wMCBo YXZlIGFza2VkIGZvciBhIFdHTEMuDQo+IA0KPiANCj4gcGxlYXNlIHByb3ZpZGUgZmVlZGJhY2sv Y29uY2VybnMvc3VnZ2VzdGVkIGFtZW5kbWVudHMgd2l0aGluIDIgd2Vla3MuDQo+IA0KPiB0aGFu a3MsDQo+IA0KPiAvaGFubmVzICYgY2hyaXMNCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fDQo+IElzaXMtd2cgbWFpbGluZyBsaXN0DQo+IElzaXMt d2dAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pc2lz LXdnDQoNCg== From nobody Thu Oct 27 05:51:27 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E98A4129449 for ; Thu, 27 Oct 2016 05:51:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.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 IzvX33nnEdM5 for ; Thu, 27 Oct 2016 05:51:21 -0700 (PDT) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0132.outbound.protection.outlook.com [104.47.38.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F1D41294C9 for ; Thu, 27 Oct 2016 05:51:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rvydlBckzW/sefYCo8WZP086oYfICHa9wb1hnp9hTKI=; b=Se+3ZqFsXCXKcKKT4EPXOhrBUia4AnOWduxQm8e+tO7tS9M5raUdRSUvJHxasC3j0tJ6gNJ+Quv9PWcM0DljX0iC3f/RRouG7wMhvhdyLWXrUW8KstpU7T+G58jCfUJyYMWaF2S7RHuDJ+sVNQXwqoPP0ftQ/daciAVYoWcYdJE= Received: from MWHPR05MB2829.namprd05.prod.outlook.com (10.168.245.11) by MWHPR05MB2832.namprd05.prod.outlook.com (10.168.245.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.679.5; Thu, 27 Oct 2016 12:51:19 +0000 Received: from MWHPR05MB2829.namprd05.prod.outlook.com ([10.168.245.11]) by MWHPR05MB2829.namprd05.prod.outlook.com ([10.168.245.11]) with mapi id 15.01.0679.015; Thu, 27 Oct 2016 12:51:19 +0000 From: Chris Bowers To: David Lamparter , "isis-wg@ietf.org list (isis-wg@ietf.org)" , "isis-chairs@tools.ietf.org" Thread-Topic: [Isis-wg] Requesting WG adoption of draft-baker-ipv6-isis-dst-src-routing-06 Thread-Index: AQHSKYc86FF4oumBi0W1MElku2Gyc6C8KTvw Date: Thu, 27 Oct 2016 12:51:19 +0000 Message-ID: References: <20161018213247.GQ639535@eidolon> In-Reply-To: <20161018213247.GQ639535@eidolon> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=cbowers@juniper.net; x-originating-ip: [66.129.239.15] x-ms-office365-filtering-correlation-id: b6616ef5-b4d1-4403-b9e1-08d3fe67f29f x-microsoft-exchange-diagnostics: 1; MWHPR05MB2832; 7:byDzlbgN605PleWPJclWmCaGMDKyrEXpbukVkO78Z4iCSTQ5Apz6o4VWbUibBg0BmwvBfQLv+RdaTgDw3Z/MopkwVpxebCqFRk5rBR90qBT3Phf4qKYxQZE3j+NjUQO+D5z/eYub97dZmqKHEJ2sKM5T5pQ0UaJkzf58jng15ccAynYWEFsP2Z9/ifd6fFV3aIv6IX+uCLyB2CE38NyS2BNhVshsbpFvzQngZ9goYOEs8T+WDi3Wy7d+YvmXKETNeo3PyyhOuNjx3TjfVFd2UaJZj2IBzylB6hgFci7oQVzBu60p/X20cn4zXOG9ltAJyEJLRvTV5fC9NA9nX7PA2oJx5uenOHbhcpdjHDwDAX8= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:MWHPR05MB2832; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(120809045254105); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026); SRVR:MWHPR05MB2832; BCL:0; PCL:0; RULEID:; SRVR:MWHPR05MB2832; x-forefront-prvs: 0108A997B2 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(13464003)(199003)(377454003)(189002)(86362001)(66066001)(33656002)(99286002)(54356999)(106116001)(106356001)(105586002)(101416001)(50986999)(76176999)(230783001)(19580405001)(19580395003)(7696004)(2950100002)(3660700001)(3280700002)(11100500001)(5660300001)(2906002)(81156014)(81166006)(2501003)(10400500002)(7736002)(7846002)(74316002)(305945005)(102836003)(4326007)(6116002)(3846002)(586003)(122556002)(87936001)(9686002)(68736007)(8936002)(92566002)(77096005)(5001770100001)(5002640100001)(97736004)(2900100001)(15975445007)(76576001)(189998001); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR05MB2832; H:MWHPR05MB2829.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Oct 2016 12:51:19.3231 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR05MB2832 Archived-At: Cc: "FredBaker.IETF@gmail.com" Subject: Re: [Isis-wg] Requesting WG adoption of draft-baker-ipv6-isis-dst-src-routing-06 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2016 12:51:26 -0000 David, I have two main comments/questions on this. 1) If I understand correctly, one reason to use existing multi-topology ro= uting mechanisms for=20 this is the requirement to support deployments where only a partial subset = of=20 routers support source address dependent routing. Ideally, this would allo= w an enterprise site to start by upgrading a subset of routers to support SADR, starting at the sit= e egress routers. =20 However, this statement from section 2.3 seems to imply that all of the rou= ters in the enterprise network would need to support multi-topology even if they don't support SADR. =20 As this compatibility mechanism is not considered optional, M-ISIS MUST therefore be implemented for supporting the protocol outlined in this document. Even installations that previously used only MTID 0 (i.e. no M-ISIS) would need to start using MTID TBD-MT0. It would be good to clarify this statement. I interpret it to mean that al= l prefix advertisements to use TLV#237, so that even routers that are currently using TLV#236 to ad= vertise IPv6 prefixes would need to start using TLV#237 instead. But it is not clear what MT-ID = a router not supporting SADR should use when advertising a prefix in TLV#237, since it can't use MT= -ID=3D0. In any case, it would be good to clarify overall if and how this solution a= chieves the goal of=20 requiring only a subset of routers to be upgraded from a basic non-MT deplo= yment of ISIS. =20 As part of this, it would be good to explain how TLV#222 and TLV#229 (the o= ther multi-topology TLVs) are used in the partial deployment case. 2) For addressing PA multi-homing for IPv6 w/o NAT in existing enterprises= , I would=20 guess that >90% of enterprises running a link-state routing protocol are ru= nning=20 OSPF as opposed to ISIS. Is the expectation that enterprises will switch t= o ISIS=20 in order to address this problem? I would like to better understand what = use cases this work=20 is targeted at from a practical point of view. Chris -----Original Message----- From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of David Lamparte= r Sent: Tuesday, October 18, 2016 4:33 PM To: isis-wg@ietf.org list (isis-wg@ietf.org) ; isis-chair= s@tools.ietf.org Cc: FredBaker.IETF@gmail.com Subject: [Isis-wg] Requesting WG adoption of draft-baker-ipv6-isis-dst-src-= routing-06 Hello IS-IS wg, I'd like to request/suggest WG adoption of draft-baker-ipv6-isis-dst-src-routing-06 [https://datatracker.ietf.org/doc/draft-baker-ipv6-isis-dst-src-routing/] which describes the IS-IS bits of source/destination routing and would also= like to head for early-allocation[*] of codepoints and MTID values (all ma= rked "TBD" in the document). The rtgwg counterpart, draft-ietf-rtgwg-dst-s= rc-routing[-02], was adopted by rtgwg a year ago. I'm also unaware of any IPR related to this draft, responding "no" to the b= oilerplate according to RFC 6702 Appendix A.3 :) The -06 version is identical to -05 except for updating Fred's author block= . I don't expect significant changes in protocol operation and am unaware = of open feedback in that direction (thus also the early-allocation request)= . As there haven't been any changes I'm unsure whether I should re-present th= e document; it'd probably end up being a repeat wasting people's time but I= 'd be happy to bring it up... Cheers, -David [*] early-allocation seems to not apply for blocks under "Expert Review" procedure, not sure if there is a process there? _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www.ietf.org/mailman/listinfo/isis-wg From nobody Thu Oct 27 07:12:48 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EBAB12964B for ; Thu, 27 Oct 2016 07:12:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 hEyCoSSwQ6TR for ; Thu, 27 Oct 2016 07:12:42 -0700 (PDT) Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a07:2ec0:2185::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAB601294B0 for ; Thu, 27 Oct 2016 07:12:42 -0700 (PDT) Received: from equinox by eidolon.nox.tf with local (Exim 4.87) (envelope-from ) id 1bzlPr-001HTF-K2; Thu, 27 Oct 2016 16:12:38 +0200 Date: Thu, 27 Oct 2016 16:12:23 +0200 From: David Lamparter To: Chris Bowers Message-ID: <20161027141223.GG639535@eidolon> References: <20161018213247.GQ639535@eidolon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Archived-At: Cc: "isis-chairs@tools.ietf.org" , "FredBaker.IETF@gmail.com" , "isis-wg@ietf.org list \(isis-wg@ietf.org\)" Subject: Re: [Isis-wg] Requesting WG adoption of draft-baker-ipv6-isis-dst-src-routing-06 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2016 14:12:47 -0000 Hi Chris, On Thu, Oct 27, 2016 at 12:51:19PM +0000, Chris Bowers wrote: > I have two main comments/questions on this. Useful feedback, Thanks! > 1) If I understand correctly, one reason to use existing multi-topology routing mechanisms for > this is the requirement to support deployments where only a partial subset of > routers support source address dependent routing. Ideally, this would allow an enterprise site to > start by upgrading a subset of routers to support SADR, starting at the site egress routers. Yes, that's the intent. > However, this statement from section 2.3 seems to imply that all of the routers in the enterprise network > would need to support multi-topology even if they don't support SADR. No, non-MT routers would be ignorant of the MT information and would not see any of the SADR routes -- which is exactly the intended goal. I'll update the draft to say this very clearly. > As this compatibility mechanism is not considered optional, M-ISIS > MUST therefore be implemented for supporting the protocol outlined in > this document. Even installations that previously used only MTID 0 > (i.e. no M-ISIS) would need to start using MTID TBD-MT0. Ah, I see where I misworded that. It needs to say "need to start using MTID TBD-MT0 *for transporting SADR routes*". Sidenote: at some point, the draft allowed non-usage of MT for greenfield setups (all routers with SADR support and everything in zero MTID / no M-ISIS used at all), with homenet in mind for that. I'm now thinking that was a stupid idea. However, there might be leftover weird wording in the draft from that. > It would be good to clarify this statement. I interpret it to mean that all prefix advertisements > to use TLV#237, so that even routers that are currently using TLV#236 to advertise IPv6 prefixes > would need to start using TLV#237 instead. But it is not clear what MT-ID a router not supporting > SADR should use when advertising a prefix in TLV#237, since it can't use MT-ID=0. No -- all non-SADR routing information stays in MTID 0/TLV 236 (or 2/237, if you're using separate IPv4/IPv6 MT topologies). There is no change to non-SADR routes, and by using a separate MTID for SADR, they will be routed "around" as non-participants in the SADR topology to ensure proper SADR operation. (That's the core idea why MT is used here.) As a nice side-effect, the operator also has some good control here in feeding information to non-SADR systems. For example, they can advertise non-SADR default routes at one or more selected SADR routers, so traffic towards the internet flows towards the "SADR subdomain", where it can then be SADR-routed to the proper exit. (MT makes sure SADR-routed traffic, once in the "SADR subdomain", will never be routed back towards non-SADR routers. They're not in the MT topology, thus not in SPF, thus not in the shortest path used for SADR routes.) > In any case, it would be good to clarify overall if and how this solution achieves the goal of > requiring only a subset of routers to be upgraded from a basic non-MT deployment of ISIS. > As part of this, it would be good to explain how TLV#222 and TLV#229 (the other multi-topology > TLVs) are used in the partial deployment case. > > 2) For addressing PA multi-homing for IPv6 w/o NAT in existing enterprises, I would > guess that >90% of enterprises running a link-state routing protocol are running > OSPF as opposed to ISIS. Is the expectation that enterprises will switch to ISIS > in order to address this problem? I would like to better understand what use cases this work > is targeted at from a practical point of view. There is/was a companion OSPF draft: https://datatracker.ietf.org/doc/draft-baker-ipv6-ospf-dst-src-routing/ which we need to revive I guess. The OSPF version has the additional constraint that it is built on another draft in progress: https://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-lsa-extend/ which led to (my personal) decision to focus on the IS-IS draft and "fix OSPF later." Sorry, OSPF ;) Updating the doc -- also planning to explain some protocol-agnostic MT considerations in the rtgwg document -- expect another mail from me soon (with a diff attached), -David From nobody Thu Oct 27 07:58:19 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 892C612956C for ; Thu, 27 Oct 2016 07:58:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.952 X-Spam-Level: X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 w_mxBgn0GPYs for ; Thu, 27 Oct 2016 07:58:14 -0700 (PDT) Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F02EE1295E0 for ; Thu, 27 Oct 2016 07:58:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5909; q=dns/txt; s=iport; t=1477580283; x=1478789883; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=c3a6EioEvto6/0cW3bR37eV9gvxBLYHbIvI7bVAzv8o=; b=TjmeaP+TYEz7vknt8UtgVdCxv7cAskF1NTVshK+5PHS7WS6WPbP+e5O6 LdPf7CWbySRp1idI8unhDHpZji8SKR4WBnln3HYdWtqqrnR+4HKrNJ8sl g4aOLJkQGU0Y/iPgypXQNyqEd+s2j1V8TmJTFcGW37I4f6wQgreynWzBo 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BiAQCqFRJY/5FdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyoBAQEBAR1YfQcBjS+Wf4dejGGCBx0LhXsCgXw/FAECAQEBAQE?= =?us-ascii?q?BAWIohGIBAQEDAQEBATc0CwwEAgEIDgMEAQEBHgkHIQYLFAkIAgQBDQUIE4gfA?= =?us-ascii?q?w8IDrwDDYNrAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWGPYNQgQWCR4FjAQEOhWw?= =?us-ascii?q?FmWE1AYYsgwiDSoMdgXWOFoccgVWEGoQAAR42X4MbHBiBOnKGKQ0XgQkBgQgBA?= =?us-ascii?q?QE?= X-IronPort-AV: E=Sophos;i="5.31,553,1473120000"; d="scan'208";a="340189286" Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Oct 2016 14:57:57 +0000 Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u9REvvjv003656 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 27 Oct 2016 14:57:57 GMT Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 27 Oct 2016 09:57:56 -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, 27 Oct 2016 09:57:56 -0500 From: "Les Ginsberg (ginsberg)" To: David Lamparter , Chris Bowers Thread-Topic: [Isis-wg] Requesting WG adoption of draft-baker-ipv6-isis-dst-src-routing-06 Thread-Index: AQHSMFDc/M48/X7CY02do40SIYDy1KC8q3aA//+u91A= Date: Thu, 27 Oct 2016 14:57:56 +0000 Message-ID: <2bb5e61dae0a44b28f066c3ce49810a1@XCH-ALN-001.cisco.com> References: <20161018213247.GQ639535@eidolon> <20161027141223.GG639535@eidolon> In-Reply-To: <20161027141223.GG639535@eidolon> 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: [128.107.147.1] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: "isis-chairs@tools.ietf.org" , "isis-wg@ietf.org list \(isis-wg@ietf.org\)" , "FredBaker.IETF@gmail.com" Subject: Re: [Isis-wg] Requesting WG adoption of draft-baker-ipv6-isis-dst-src-routing-06 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2016 14:58:18 -0000 David - > -----Original Message----- > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of David > Lamparter > Sent: Thursday, October 27, 2016 7:12 AM > To: Chris Bowers > Cc: isis-chairs@tools.ietf.org; FredBaker.IETF@gmail.com; isis-wg@ietf.or= g > list (isis-wg@ietf.org) > Subject: Re: [Isis-wg] Requesting WG adoption of draft-baker-ipv6-isis-ds= t- > src-routing-06 >=20 > Hi Chris, >=20 > On Thu, Oct 27, 2016 at 12:51:19PM +0000, Chris Bowers wrote: > > I have two main comments/questions on this. >=20 > Useful feedback, Thanks! >=20 > > 1) If I understand correctly, one reason to use existing > > multi-topology routing mechanisms for this is the requirement to > > support deployments where only a partial subset of routers support > > source address dependent routing. Ideally, this would allow an enterpr= ise > site to start by upgrading a subset of routers to support SADR, starting = at the > site egress routers. >=20 > Yes, that's the intent. >=20 > > However, this statement from section 2.3 seems to imply that all of > > the routers in the enterprise network would need to support multi- > topology even if they don't support SADR. >=20 > No, non-MT routers would be ignorant of the MT information and would not > see any of the SADR routes -- which is exactly the intended goal. I'll u= pdate > the draft to say this very clearly. >=20 [Les:] For my taste the best way to do this is simply to remove the stateme= nt: " Even installations that previously used only MTID 0 (i.e. no M-ISIS) would need to start using MTID TBD-MT0." You don't need to explain the way MT works because you are making no change= s to RFC 5120. Trying to "explain" is only going put you at risk for misint= erpretation - and this thread is an existence proof for that. :-) It is the first sentence of the same paragraph which is important: " As this compatibility mechanism is not considered optional, M-ISIS MUST therefore be implemented for supporting the protocol outlined in this document." (though I would prefer replacing "protocol" with "extensions") Les > > As this compatibility mechanism is not considered optional, M-ISIS > > MUST therefore be implemented for supporting the protocol outlined i= n > > this document. Even installations that previously used only MTID 0 > > (i.e. no M-ISIS) would need to start using MTID TBD-MT0. >=20 > Ah, I see where I misworded that. It needs to say "need to start using M= TID > TBD-MT0 *for transporting SADR routes*". >=20 > Sidenote: at some point, the draft allowed non-usage of MT for greenfiel= d > setups (all routers with SADR support and everything in zero MTID / no M- > ISIS used at all), with homenet in mind for that. I'm now thinking that = was a > stupid idea. However, there might be leftover weird wording in the draft > from that. >=20 > > It would be good to clarify this statement. I interpret it to mean > > that all prefix advertisements to use TLV#237, so that even routers > > that are currently using TLV#236 to advertise IPv6 prefixes would need > > to start using TLV#237 instead. But it is not clear what MT-ID a route= r not > supporting SADR should use when advertising a prefix in TLV#237, since it > can't use MT-ID=3D0. >=20 > No -- all non-SADR routing information stays in MTID 0/TLV 236 (or 2/237,= if > you're using separate IPv4/IPv6 MT topologies). There is no change to no= n- > SADR routes, and by using a separate MTID for SADR, they will be routed > "around" as non-participants in the SADR topology to ensure proper SADR > operation. (That's the core idea why MT is used > here.) >=20 >=20 > As a nice side-effect, the operator also has some good control here in > feeding information to non-SADR systems. For example, they can advertise > non-SADR default routes at one or more selected SADR routers, so traffic > towards the internet flows towards the "SADR subdomain", where it can > then be SADR-routed to the proper exit. >=20 > (MT makes sure SADR-routed traffic, once in the "SADR subdomain", will > never be routed back towards non-SADR routers. They're not in the MT > topology, thus not in SPF, thus not in the shortest path used for SADR > routes.) >=20 > > In any case, it would be good to clarify overall if and how this > > solution achieves the goal of requiring only a subset of routers to be > upgraded from a basic non-MT deployment of ISIS. > > As part of this, it would be good to explain how TLV#222 and TLV#229 > > (the other multi-topology > > TLVs) are used in the partial deployment case. > > > > 2) For addressing PA multi-homing for IPv6 w/o NAT in existing > > enterprises, I would guess that >90% of enterprises running a > > link-state routing protocol are running OSPF as opposed to ISIS. Is th= e > expectation that enterprises will switch to ISIS > > in order to address this problem? I would like to better understand w= hat > use cases this work > > is targeted at from a practical point of view. >=20 > There is/was a companion OSPF draft: > https://datatracker.ietf.org/doc/draft-baker-ipv6-ospf-dst-src-routing/ > which we need to revive I guess. The OSPF version has the additional > constraint that it is built on another draft in progress: > https://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-lsa-extend/ > which led to (my personal) decision to focus on the IS-IS draft and "fix = OSPF > later." Sorry, OSPF ;) >=20 >=20 > Updating the doc -- also planning to explain some protocol-agnostic MT > considerations in the rtgwg document -- expect another mail from me soon > (with a diff attached), >=20 >=20 > -David >=20 > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg From nobody Thu Oct 27 19:03:29 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C05FA1294FE for ; Thu, 27 Oct 2016 19:03:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 kb1I4f1-YP3e for ; Thu, 27 Oct 2016 19:03:24 -0700 (PDT) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7032E129440 for ; Thu, 27 Oct 2016 19:03:24 -0700 (PDT) Received: by mail-oi0-x232.google.com with SMTP id y2so91734646oie.0 for ; Thu, 27 Oct 2016 19:03:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fm01rJEbCilD020pD5G/VJMvkRdfVKcTET0FdQLC5dQ=; b=hgRfOt/yqHBykEyVgQdgtlwdC8ppz874FGJYuUndmqZ/7naOJV7njGGC/tyvo46UX6 zlpqWWKbI5brFZNXrJ21wePdK/IsnCrRQlS8B5PFJ6J/HJfBRJV6SlUDvg5D7JuCa8I6 9B2tFJAAHBi5VgPht4/r1M/HXz4g0Kh+niPZGTWcuTIrviX/Op+T7hR+lmBKSLuJCWvq yDm6IpO7Jh/9xf46226nzoyfMukyynTlo0GsKKof6WXo9s7htGU5vfuz6b7GiJOuqNtj +RvXajVwhkEuFqajqzwZf7d+8kjf1awCaJjvYwd7XIJu/KMNlBFrHT+tWcp9jmdywCJe 1cfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fm01rJEbCilD020pD5G/VJMvkRdfVKcTET0FdQLC5dQ=; b=PTUxwf7oxG0PR+UczSCLphuK+b6J7gq2JVLX0e1mZL14eR5XM4Oz5DsMvT5/LKV9I1 EuTj6pi7naT7emHR1prC+P0vBykCaDURkvVPJBXvQADSpuiyfhh36EV7AXnM7ImI6gsI dCnVLrOS++/P2GyCMLh78aGdsj9vutahPrwLtI8lJC+6ZRBh+lKnuyebMzBPUxdoyX3O WOiBzRH+D/MZew9Y/igJbHTYzmaWna8pxui4GRAncN4+ZI4BzJceRavZORWZj79DSaEK i70HPye7lOL5j5OFzEhwygx0n2avmqtNqy/gxS0vLjTG5U6vfNz3r+f3gHnwQ/S+/i6L FIsw== X-Gm-Message-State: ABUngvfhT1M67/sTRpP3HAB+78MIj88di1otfTl2rNgF+EiI+ZqV8STK5/vDRMst7u+1Mom1gH1amtz/7mMmBw== X-Received: by 10.107.36.144 with SMTP id k138mr8674155iok.201.1477620203783; Thu, 27 Oct 2016 19:03:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.6.214 with HTTP; Thu, 27 Oct 2016 19:02:43 -0700 (PDT) In-Reply-To: <20161027141223.GG639535@eidolon> References: <20161018213247.GQ639535@eidolon> <20161027141223.GG639535@eidolon> From: Tony Przygienda Date: Thu, 27 Oct 2016 19:02:43 -0700 Message-ID: To: David Lamparter Content-Type: multipart/alternative; boundary=001a11402d105c0c9d053fe343d6 Archived-At: Cc: "isis-chairs@tools.ietf.org" , "isis-wg@ietf.org list \(isis-wg@ietf.org\)" , "FredBaker.IETF@gmail.com" Subject: Re: [Isis-wg] Requesting WG adoption of draft-baker-ipv6-isis-dst-src-routing-06 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2016 02:03:27 -0000 --001a11402d105c0c9d053fe343d6 Content-Type: text/plain; charset=UTF-8 On Thu, Oct 27, 2016 at 7:12 AM, David Lamparter wrote: > Hi Chris, > > On Thu, Oct 27, 2016 at 12:51:19PM +0000, Chris Bowers wrote: > > I have two main comments/questions on this. > > Useful feedback, Thanks! > > > 1) If I understand correctly, one reason to use existing multi-topology > routing mechanisms for > > this is the requirement to support deployments where only a partial > subset of > > routers support source address dependent routing. Ideally, this would > allow an enterprise site to > > start by upgrading a subset of routers to support SADR, starting at the > site egress routers. > > Yes, that's the intent. > > > However, this statement from section 2.3 seems to imply that all of the > routers in the enterprise network > > would need to support multi-topology even if they don't support SADR. > > No, non-MT routers would be ignorant of the MT information and would not > see any of the SADR routes -- which is exactly the intended goal. I'll > update the draft to say this very clearly. > > > As this compatibility mechanism is not considered optional, M-ISIS > > MUST therefore be implemented for supporting the protocol outlined in > > this document. Even installations that previously used only MTID 0 > > (i.e. no M-ISIS) would need to start using MTID TBD-MT0. > > Ah, I see where I misworded that. It needs to say "need to start using > MTID TBD-MT0 *for transporting SADR routes*". > > Sidenote: at some point, the draft allowed non-usage of MT for > greenfield setups (all routers with SADR support and everything in zero > MTID / no M-ISIS used at all), with homenet in mind for that. I'm now > thinking that was a stupid idea. However, there might be leftover weird > wording in the draft from that. > My first comment a good while ago on the mike when you were showing your first proposals was that you'll on a slippery slope to redo MT in topology #0 ;-) Stupid is too strong a word, it's simply one of those problems that looks like a "small addition" needed initially until it sucks you treacherously underwater. I favor adoption as well as an elegant application of MT with the following necessary fixes ;-) a) you prescribe 2 different things in the draft ;-) a.1 you want to forklift all the routers in section 2.3. In fact, MT-ISIS has been proposed to prevent such fork-lifting need. Forklifting is sufficient but not necessary as you observe later in the "correctness considerations". a.2 in "correctness considerations" you allow to mix the routers which is correct but the logical chain doesn't hold completely. First "axiom" is clear (i.e. forwarding lookup). The second "pilar" is confused by *"If, for case (b1), the system knows of the existence of a more* * specific D/S route, but cannot calculate a valid path, it may* * either apply non-D/S routing (i.e. not install any route) or* * discard the packet (i.e. install a discard route). The next hop* * will either be a non-D/S system, or a D/S system with the same* * link-state information (and thus again unable to calculate a valid* * path -- or, more specifically, won't calculate a path that* * includes the previous router)."* That seems to contradict *"**Packets will transit into D/S routing but not out of it"* In short, with your axiom (prefer routes with source match over 0/0 source entry) you have two choices for the 2nd axiom (both lead to correct routing but exclude each other). The reason is that you either "enter semantically richer topology and never leave" _OR_ "exit semantically richer semantics and never enter it again". Less formally that translates into Either a) a packet may enter from non D/S into D/S and any D/S MUST NOT forward it to a non D/S next-hop, i.e. you can't install default topology entries into FIB as "union". This holds EVEN when you received the packet from a D/S neighbor since the packet MUST NOT jump out into the non-D/S topo again (it may have came from here upstream). Otherwise you'll find looping scenarios or b) a packet may exit from D/S into non-D/S, i.e. no source-specific FIB match is found and you match on 0/0 source (topology #0). Once it's out in the non-DS world, it MUST stay there, i.e. you must not as D/S router advertise topology #0 information since a non-DS router may use that to jump into the D/S again not understanding it's doing it. Again, in short you either enter D/S once and only once and never leave D/S or you exit D/S once and only once and never enter D/S again. b) section 3.1: I would explain what is the multiplicity of this TLV and I expect it to be 1 and only 1. Omitting it will collide with MTID#0 and having two has no semantics (unless specified). --- tony --001a11402d105c0c9d053fe343d6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Thu, Oct 27, 2016 a= t 7:12 AM, David Lamparter <equinox@diac24.net> wrote:
<= /font>
Hi Chris,

On Thu, Oct 27, 2016 at 12:51:19PM +0000, Chris Bowers wrote:
> I have two main comments/questions on this.

Useful feedback, Thanks!

> 1)=C2=A0 If I understand correctly, one reason to use existing multi-t= opology routing mechanisms for
> this is the requirement to support deployments where only a partial su= bset of
> routers support source address dependent routing.=C2=A0 Ideally, this = would allow an enterprise site to
> start by upgrading a subset of routers to support SADR, starting at th= e site egress routers.

Yes, that's the intent.

> However, this statement from section 2.3 seems to imply that all of th= e routers in the enterprise network
> would need to support multi-topology even if they don't support SA= DR.

No, non-MT routers would be ignorant of the MT information and would= not
see any of the SADR routes -- which is exactly the intended goal.=C2=A0 I&#= 39;ll
update the draft to say this very clearly.

>=C2=A0 =C2=A0 As this compatibility mechanism is not considered optiona= l, M-ISIS
>=C2=A0 =C2=A0 MUST therefore be implemented for supporting the protocol= outlined in
>=C2=A0 =C2=A0 this document.=C2=A0 Even installations that previously u= sed only MTID 0
>=C2=A0 =C2=A0 (i.e.=C2=A0 no M-ISIS) would need to start using MTID TBD= -MT0.

Ah, I see where I misworded that.=C2=A0 It needs to say "need t= o start using
MTID TBD-MT0 *for transporting SADR routes*".

Sidenote:=C2=A0 at some point, the draft allowed non-usage of MT for
greenfield setups (all routers with SADR support and everything in zero
MTID / no M-ISIS used at all), with homenet in mind for that.=C2=A0 I'm= now
thinking that was a stupid idea.=C2=A0 However, there might be leftover wei= rd
wording in the draft from that.


My first comm= ent a good while ago on the mike when you were showing your first
proposals was that you'll o= n a slippery slope to=C2=A0
redo MT in topology #0 ;-) =C2=A0Stupid is too strong a word, it'= s simply one of those=C2=A0
problems that looks like a "small addition" needed initially until it sucks you= =C2=A0
tre= acherously underwater. =C2=A0

I favor a= doption as well as an elegant application of MT with the following=C2=A0
necessary fixes ;-)=C2= =A0

a) you prescribe 2 d= ifferent things in the draft ;-)=C2=A0

= =C2=A0 =C2=A0a.1 =C2=A0you want to forklift all the routers in section 2.3.= In fact, MT-ISIS has=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 been proposed to prevent such fork-liftin= g need. Forklifting is sufficient=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 but not necessary as you obse= rve later in the "correctness considerations".=C2=A0
=
=C2=A0 =C2=A0a.2 =C2=A0in "co= rrectness considerations" you allow to mix the routers which is correc= t
=C2=A0 =C2=A0 =C2=A0= =C2=A0 but the logical chain doesn't hold completely.=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Firs= t=C2=A0"axiom&q= uot; is clear (i.e. forwarding lookup). The second=C2=A0
<= span style=3D"font-family:monospace,monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 = "pilar" =C2=A0is confused by=C2=A0

=C2=A0 =C2=A0 =C2=A0 "If, for case (b1), the system knows of the existence of a mo= re
specific D/S route, but = cannot calculate a valid path, it may
= either apply non-D/S routing (i.e. not install any route) or
discard the packet (i.e. install a discard= route). The next hop
will either= be a non-D/S system, or a D/S system with the same
link-state information (and thus again unable to calculat= e a valid
path -- or, more specifi= cally, won't calculate a path that
= includes the previous router)."
      That seems to contradict "<=
/span>Packets will trans=
it into D/S routing but not out of it"
=C2=A0 =C2=A0 =C2=A0
=C2=A0 =C2=A0 =C2=A0 In short, with your axiom= (prefer routes with source match over 0/0 source entry)
<= font face=3D"monospace, monospace">=C2=A0 =C2=A0 =C2=A0 you have two choice= s for the 2nd axiom (both lead to correct routing=C2=A0
=C2=A0 =C2=A0 =C2=A0 but exclude each oth= er).=C2=A0The reason is that you either "enter semantically=C2=A0
=C2=A0 =C2=A0 =C2=A0 riche= r topology and never leave" _OR_ "exit semantically richer=C2=A0s= emantics and
=C2=A0 = =C2=A0 =C2=A0 never enter it again". Less formally that translates int= o

=C2=A0 =C2=A0 =C2=A0 Either=C2=A0

=C2=A0 =C2=A0 =C2=A0 a) a packet may enter= from non D/S into D/S and any D/S MUST NOT=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0forward it to= a non D/S next-hop, i.e. you can't install=C2=A0default topology=C2=A0=
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0entries into FIB as "union".=C2=A0This holds EVEN wh= en you received the=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0packet from a D/S neighbor since the = packet MUST NOT jump out into=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the non-D/S=C2=A0topo again= (it may have came from here upstream). Otherwise=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0you'= ;ll find=C2=A0looping scenarios=C2=A0

= =C2=A0 =C2=A0 =C2=A0 or=C2=A0

=C2=A0 = =C2=A0 =C2=A0 b) a packet may exit from D/S into non-D/S, i.e. no source-sp= ecific FIB match=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0is found and you match on 0/0 source (to= pology #0). Once it's out in the=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0non-DS world, it MUS= T stay there, i.e. you must not as D/S router advertise=C2=A0
<= div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0t= opology #0 information since a non-DS router may use=C2=A0that to jump into= =C2=A0
=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0the D/S again not understanding it's doing it.=C2= =A0

<= div>=C2=A0 =C2=A0 =C2=A0 Again, in shor= t you either enter D/S once and only once and never leave D/S or you=C2=A0<= /font>
=C2=A0 =C2=A0 =C2=A0 e= xit D/S once and only once and never enter D/S again.=C2=A0


= b) section 3.1: I would explain what is= the multiplicity of this TLV and I expect it=C2=A0
=C2=A0 =C2=A0to be 1 and only 1. Omitting it = will collide with MTID#0 and having two has no=C2=A0
=C2=A0 =C2=A0semantics (unless specified).= =C2=A0


--- tony=C2=A0
=C2=A0 =C2=A0

=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0

--001a11402d105c0c9d053fe343d6-- From nobody Thu Oct 27 20:56:01 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56630126CD8 for ; Thu, 27 Oct 2016 20:56:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.921 X-Spam-Level: X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 kqt12Iwn-mN6 for ; Thu, 27 Oct 2016 20:55:55 -0700 (PDT) Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 683481295F8 for ; Thu, 27 Oct 2016 20:55:55 -0700 (PDT) Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id C37087E7BF047; Fri, 28 Oct 2016 03:55:52 +0000 (GMT) Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u9S3tqTN012780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 28 Oct 2016 03:55:52 GMT Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u9S3tpaa000580 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 28 Oct 2016 05:55:52 +0200 Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.36]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0301.000; Fri, 28 Oct 2016 05:53:30 +0200 From: "Henderickx, Wim (Nokia - BE)" To: Hannes Gredler , "Les Ginsberg (ginsberg)" , "chopps@chopps.org" , "isis-wg@ietf.org list (isis-wg@ietf.org)" Thread-Topic: WGLC for draft-ietf-isis-mi-bis-00.txt Thread-Index: AdIrFJJKwg1uaP+eQXa5SqdoBR7OxgCtIpgAABnWCAAAmN84AA== Date: Fri, 28 Oct 2016 03:53:29 +0000 Message-ID: References: <6496deea-46c2-9cbc-5771-5d2276c2b5d5@rtbrick.com> In-Reply-To: Accept-Language: nl-BE, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/f.1b.0.161010 x-originating-ip: [135.239.27.41] Content-Type: text/plain; charset="utf-8" Content-ID: <9FCE1563B027864DB6E735E24BCC8ED9@exchange.lucent.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: Cc: "Stefano Previdi \(sprevidi\)" Subject: Re: [Isis-wg] WGLC for draft-ietf-isis-mi-bis-00.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2016 03:56:00 -0000 Rm9yZ290IHRvIGFkZCBpc2lzIFdHIGxpc3QNCg0KT24gMjQvMTAvMjAxNiwgMjE6NTUsICJIZW5k ZXJpY2t4LCBXaW0gKE5va2lhIC0gQkUpIiA8d2ltLmhlbmRlcmlja3hAbm9raWEuY29tPiB3cm90 ZToNCg0KICAgIEkgYW0gbm90IGF3YXJlIG9mIElQUiByZWxhdGVkIHRvIHRoaXMgZHJhZnQNCiAg ICANCiAgICBPbiAyNC8xMC8yMDE2LCAxMTozNCwgIkhhbm5lcyBHcmVkbGVyIiA8aGFubmVzQHJ0 YnJpY2suY29tPiB3cm90ZToNCiAgICANCiAgICAgICAgZ3Vlc3MgdGhlIElQUiBkZWNsYXJhdGlv biBvZiBhdXRob3JzIGlzIHlldCBtaXNzaW5nIC4uLg0KICAgICAgICANCiAgICAgICAgcGxlYXNl IG1ha2UgdGhhdCBhbmQgaSdsbCBwdXNoIGl0IHRvIHRoZSByZmMtZWQgcXVldWUuDQogICAgICAg IA0KICAgICAgICAvaGFubmVzDQogICAgICAgIA0KICAgICAgICBPbiAxMC8yMC8xNiAyMzowMCwg TGVzIEdpbnNiZXJnIChnaW5zYmVyZykgd3JvdGU6DQogICAgICAgID4gQ2hyaXMvSGFubmVzIC0N CiAgICAgICAgPg0KICAgICAgICA+IEluIEJlcmxpbiBJIHByZXNlbnRlZCBkcmFmdC1pZXRmLWlz aXMtbWktYmlzLTAwLnR4dC4gDQogICAgICAgID4gSXQgd2FzIHBvaW50ZWQgb3V0IHRoYXQgd2Ug aGF2ZSB0d28gaW1wbGVtZW50YXRpb25zIHdoaWNoIGhhdmUgYmVlbiB0ZXN0ZWQgZm9yIGludGVy b3BlcmFiaWxpbGl0eSBhbmQgbm8gcmVzcG9uc2UgaGFzIGJlZW4gcmVjZWl2ZWQgcmVnYXJkaW5n IHBvc3NpYmxlIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5IGlzc3VlcyBzaW5jZSB0aGUgZG9jdW1l bnQgYmVjYW1lIGEgV0cgZG9jdW1lbnQgaW4gTWF5IGFuZCB3ZSBhc2tlZCB0aGUgcXVlc3Rpb24u DQogICAgICAgID4gSSBjb25jbHVkZWQgdGhlIHByZXNlbnRhdGlvbiBieSByZXF1ZXN0aW5nIFdH TEMgLSBidXQgbm8gYWN0aW9uIHdhcyB0YWtlbi4NCiAgICAgICAgPg0KICAgICAgICA+IENhbiB3 ZSBpbml0aWF0ZSBXR0xDPw0KICAgICAgICA+DQogICAgICAgID4gICAgTGVzDQogICAgICAgID4N CiAgICAgICAgDQogICAgICAgIA0KICAgIA0KICAgIA0KDQo= From nobody Fri Oct 28 09:54:31 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50686129847 for ; Fri, 28 Oct 2016 09:54:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.951 X-Spam-Level: X-Spam-Status: No, score=-14.951 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.431, 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 fPh7Tk8NvO7A for ; Fri, 28 Oct 2016 09:54:25 -0700 (PDT) Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF6BB12961A for ; Fri, 28 Oct 2016 09:54:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9224; q=dns/txt; s=iport; t=1477673664; x=1478883264; h=from:to:subject:date:message-id:references:mime-version; bh=VdP8XtQWiRzH5aIADwzIbw57S23SoNuV5FidVZohmjo=; b=LQrrKVLCjKopBnnbYnJF7mvv94D7AQOfwJxkoUs1c+etOFotqGTc/cQ7 5rGmuNt2xCa5JMTD/4TDgaoAgNZy5thZ6YxkQyq4Ku5ig0GNn+nijz8Jd xFQIHNvalQ0tAYa6SbR0yMNGw0ikmWjMUh+MjdKcF4K45e5cD47+M0yXm I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BvAQAXghNY/5pdJa1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgyoBAQEBAR9YfQeNL5Z/jymFFoIHHQEKhXsCgX8/FAECAQEBAQEBAWI?= =?us-ascii?q?ohGIBAQEEAQEBawQXAgEZAwECKAcnCxQHAggCBBMJiEsOvVsBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEciDoIglCEZxaCFmSCLwWUOoVeAYYsiXqBbk6EH4gCgSeJDYQ?= =?us-ascii?q?ChAABHjYiPYUKcgGGaYEJAQEB?= X-IronPort-AV: E=Sophos;i="5.31,410,1473120000"; d="scan'208,217";a="167909456" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Oct 2016 16:54:23 +0000 Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u9SGsNJq022556 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Fri, 28 Oct 2016 16:54:23 GMT Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 28 Oct 2016 11:54:23 -0500 Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1210.000; Fri, 28 Oct 2016 11:54:23 -0500 From: "Naiming Shen (naiming)" To: "isis-wg@ietf.org list" Thread-Topic: I-D Action: draft-shen-isis-spine-leaf-ext-02.txt Thread-Index: AQHSMNpCYCnpAThhwUqrfJJka4mFFg== Date: Fri, 28 Oct 2016 16:54:23 +0000 Message-ID: <3D9BD9EA-1BB4-4894-95B4-F473C76C1743@cisco.com> References: <147763168616.24626.7829532685736002572.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.24.82.80] Content-Type: multipart/alternative; boundary="_000_3D9BD9EA1BB4489495B4F473C76C1743ciscocom_" MIME-Version: 1.0 Archived-At: Subject: [Isis-wg] Fwd: I-D Action: draft-shen-isis-spine-leaf-ext-02.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2016 16:54:27 -0000 --_000_3D9BD9EA1BB4489495B4F473C76C1743ciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, We have updated the spine-leaf draft, o Removed the 'Default Route Metric' field in the Spine-Leaf TLV and changed to using the IS-IS Reverse Metric in IIH. Please review and comment. thanks. - Naiming Begin forwarded message: From: internet-drafts@ietf.org Subject: I-D Action: draft-shen-isis-spine-leaf-ext-02.txt Date: October 27, 2016 at 10:14:46 PM PDT To: > Reply-To: internet-drafts@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts director= ies. Title : IS-IS Routing for Spine-Leaf Topology Authors : Naiming Shen Sanjay Thyamagundalu Filename : draft-shen-isis-spine-leaf-ext-02.txt Pages : 12 Date : 2016-10-27 Abstract: This document describes a mechanism for routers and switches in Spine-Leaf type topology to have non-reciprocal Intermediate System to Intermediate System (IS-IS) routing relationships between the leafs and spines. The leaf nodes do not need to have the topology information of other nodes and exact prefixes in the network. This extension also has application in the Internet of Things (IoT). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-shen-isis-spine-leaf-ext/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-shen-isis-spine-leaf-ext-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=3Ddraft-shen-isis-spine-leaf-ext-02 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --_000_3D9BD9EA1BB4489495B4F473C76C1743ciscocom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable

Hi,

We have updated the spine-leaf draft,

   o  Removed the 'Default Route Metric' fie= ld in the Spine-Leaf TLV and
      changed to using the IS-IS Reverse Met= ric in IIH.

Please review and comment.

thanks.
- Naiming

Begin forwarded message:

Subject: I-D Action: draft-shen-is= is-spine-leaf-ext-02.txt
Date: October 27, 2016 at 10:14:46 PM PDT


A New Internet-Draft is available from the on-line Internet-Drafts director= ies.


       Title     &nb= sp;     : IS-IS Routing for Spine-Leaf Topology        Authors     &= nbsp;   : Naiming Shen
            &nb= sp;            = Sanjay Thyamagundalu
Filename &n= bsp;      : draft-shen-isis-spine-leaf-ext-02= .txt
Pages  = ;         : 12
Date  =           : 2016-10-27
Abstract:
  This document describes a mechanism for routers and switches in=
  Spine-Leaf type topology to have non-reciprocal Intermediate Sy= stem
  to Intermediate System (IS-IS) routing relationships between th= e
  leafs and spines.  The leaf nodes do not need to have the = topology
  information of other nodes and exact prefixes in the network. &= nbsp;This
  extension also has application in the Internet of Things (IoT).=


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-shen-isis-spine-leaf-ex= t/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-shen-isis-spine-leaf-ext-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-shen-isis-spine-leaf-ext-02


Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--_000_3D9BD9EA1BB4489495B4F473C76C1743ciscocom_-- From nobody Fri Oct 28 13:58:49 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F920129695 for ; Fri, 28 Oct 2016 13:58:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.951 X-Spam-Level: X-Spam-Status: No, score=-14.951 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.431, 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 bOgmx6KCioM1 for ; Fri, 28 Oct 2016 13:58:35 -0700 (PDT) Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24E32129694 for ; Fri, 28 Oct 2016 13:58:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11322; q=dns/txt; s=iport; t=1477688312; x=1478897912; h=from:to:subject:date:message-id:references:mime-version; bh=DYJ+Zwd8acjFGzAohPTjgELrVVTxE4D/YJTp4hauMgg=; b=W+LCu3xj06pMZdfBfrAWk29JcZXg0VUNRbrb1UZwiAlqWib5QR551A7n SzdkIml+bGjrj/B7/KK+zxAfxvP8pmHhZeLRwoe1NVT9Wg894CLGi60Fo noJb4SuregqTNdR1qVbiht8wtJe/bx8DbB9xSBnS8Dx1PzcLbEOJ5dNxQ c=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0COAQA6uxNY/4kNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgyoBAQEBAR9YfQcBjS6Wf48phRaCBx0BCoV7AhqBaj8UAQIBAQEBAQE?= =?us-ascii?q?BYiiEYgEBAQQBAQEgRAcbAgEZAwECKAMCAgIlCxQHAggCBBMJiEsOsV2MZwEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBARyIOgiCUIRnFoIWOCyCLwWUOoVeAYYsiXqBbk6?= =?us-ascii?q?EH4gCgSeJDYQChAABHjYiPYUKcgGGaQGBCAEBAQ?= X-IronPort-AV: E=Sophos;i="5.31,411,1473120000"; d="scan'208,217";a="339753779" Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Oct 2016 20:58:31 +0000 Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u9SKwVBJ024361 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Fri, 28 Oct 2016 20:58:31 GMT Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 28 Oct 2016 15:58:31 -0500 Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1210.000; Fri, 28 Oct 2016 15:58:30 -0500 From: "Naiming Shen (naiming)" To: "isis-wg@ietf.org list" Thread-Topic: I-D Action: draft-shen-isis-geo-coordinates-02.txt Thread-Index: AQHSMVxnms02RfXAfEaFL00I+EIovw== Date: Fri, 28 Oct 2016 20:58:30 +0000 Message-ID: <4156A736-6F7D-4577-BBFF-527C185DD238@cisco.com> References: <147768758692.24947.15213581322700083034.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [128.107.155.81] Content-Type: multipart/alternative; boundary="_000_4156A7366F7D4577BBFF527C185DD238ciscocom_" MIME-Version: 1.0 Archived-At: Subject: [Isis-wg] Fwd: I-D Action: draft-shen-isis-geo-coordinates-02.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2016 20:58:41 -0000 --_000_4156A7366F7D4577BBFF527C185DD238ciscocom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 DQpIaSwNCg0KQSBuZXcgdmVyc2lvbiBvZiBnZW8tbG9jYXRpb24gaXMgcG9zdGVkLCB0aGUgY2hh bmdlIGlzIHRvDQppbmNsdWRlIHRoZSDigJhSYWRpdXPigJkgZmllbGQgKHRvIGJlIGNvbXBhdGli bGUgd2l0aCBMSVNQ4oCZcw0KcHJvcG9zY2FsKSwgYW5kIGEgUHJpdmFjeSBzZWN0aW9uLg0KDQpQ bGVhc2UgcmV2aWV3IGFuZCBjb21tZW50Lg0KDQp0aGFua3MuDQotIE5haW1pbmcNCg0KQmVnaW4g Zm9yd2FyZGVkIG1lc3NhZ2U6DQoNCkZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZzxtYWls dG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnPg0KU3ViamVjdDogSS1EIEFjdGlvbjogZHJhZnQt c2hlbi1pc2lzLWdlby1jb29yZGluYXRlcy0wMi50eHQNCkRhdGU6IE9jdG9iZXIgMjgsIDIwMTYg YXQgMTo0NjoyNiBQTSBQRFQNClRvOiA8aS1kLWFubm91bmNlQGlldGYub3JnPG1haWx0bzppLWQt YW5ub3VuY2VAaWV0Zi5vcmc+Pg0KUmVwbHktVG86IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZzxt YWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnPg0KDQoNCkEgTmV3IEludGVybmV0LURyYWZ0 IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmll cy4NCg0KDQogICAgICAgVGl0bGUgICAgICAgICAgIDogQ2FycnlpbmcgR2VvIENvb3JkaW5hdGVz IEluZm9ybWF0aW9uIEluIElTLUlTDQogICAgICAgQXV0aG9ycyAgICAgICAgIDogTmFpbWluZyBT aGVuDQogICAgICAgICAgICAgICAgICAgICAgICAgRW5rZSBDaGVuDQogICAgICAgICAgICAgICAg ICAgICAgICAgQWNlZSBMaW5kZW4NCkZpbGVuYW1lICAgICAgICA6IGRyYWZ0LXNoZW4taXNpcy1n ZW8tY29vcmRpbmF0ZXMtMDIudHh0DQpQYWdlcyAgICAgICAgICAgOiA5DQpEYXRlICAgICAgICAg ICAgOiAyMDE2LTEwLTI4DQoNCkFic3RyYWN0Og0KICBUaGlzIGRvY3VtZW50IGRlZmluZXMgYSBu ZXcgSVMtSVMgVExWIHdoaWNoIGNhcnJpZXMgdGhlIEdlbw0KICBDb29yZGluYXRlcyBpbmZvcm1h dGlvbiBvZiB0aGUgc3lzdGVtLiAgVGhlIEdlbyBDb29yZGluYXRlcw0KICBpbmZvcm1hdGlvbiBj YW4gYmUgdXNlZCBieSBJUy1JUyByb3V0aW5nIG9yIGJ5IGFueSBhcHBsaWNhdGlvbnMuDQoNCg0K VGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6DQpodHRw czovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1zaGVuLWlzaXMtZ2VvLWNvb3JkaW5h dGVzLw0KDQpUaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDoNCmh0 dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1zaGVuLWlzaXMtZ2VvLWNvb3JkaW5hdGVz LTAyDQoNCkEgZGlmZiBmcm9tIHRoZSBwcmV2aW91cyB2ZXJzaW9uIGlzIGF2YWlsYWJsZSBhdDoN Cmh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1zaGVuLWlzaXMtZ2VvLWNv b3JkaW5hdGVzLTAyDQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBv ZiBtaW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KdW50aWwgdGhlIGh0bWxpemVk IHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCg0KSW50 ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0KZnRw Oi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCg0KX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5vdW5jZSBtYWlsaW5nIGxpc3QNCkkt RC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m by9pLWQtYW5ub3VuY2UNCkludGVybmV0LURyYWZ0IGRpcmVjdG9yaWVzOiBodHRwOi8vd3d3Lmll dGYub3JnL3NoYWRvdy5odG1sDQpvciBmdHA6Ly9mdHAuaWV0Zi5vcmcvaWV0Zi8xc2hhZG93LXNp dGVzLnR4dA0KDQo= --_000_4156A7366F7D4577BBFF527C185DD238ciscocom_ Content-Type: text/html; charset="utf-8" Content-ID: <5592AEF22185074289A09A7956B10EC3@emea.cisco.com> Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj48YnIgY2xh c3M9IiI+DQo8L2Rpdj4NCkhpLA0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4N CjxkaXYgY2xhc3M9IiI+QSBuZXcgdmVyc2lvbiBvZiBnZW8tbG9jYXRpb24gaXMgcG9zdGVkLCB0 aGUgY2hhbmdlIGlzIHRvPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPmluY2x1ZGUgdGhlIOKAmFJhZGl1 c+KAmSBmaWVsZCAodG8gYmUgY29tcGF0aWJsZSB3aXRoIExJU1DigJlzPC9kaXY+DQo8ZGl2IGNs YXNzPSIiPnByb3Bvc2NhbCksIGFuZCBhIFByaXZhY3kgc2VjdGlvbi48L2Rpdj4NCjxkaXYgY2xh c3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPlBsZWFzZSByZXZpZXcg YW5kIGNvbW1lbnQuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0K PGRpdiBjbGFzcz0iIj50aGFua3MuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPi0gTmFpbWluZzxiciBj bGFzcz0iIj4NCjxkaXY+PGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xh c3M9IiI+DQo8ZGl2IGNsYXNzPSIiPkJlZ2luIGZvcndhcmRlZCBtZXNzYWdlOjwvZGl2Pg0KPGJy IGNsYXNzPSJBcHBsZS1pbnRlcmNoYW5nZS1uZXdsaW5lIj4NCjxkaXYgc3R5bGU9Im1hcmdpbi10 b3A6IDBweDsgbWFyZ2luLXJpZ2h0OiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgbWFyZ2luLWxl ZnQ6IDBweDsiIGNsYXNzPSIiPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiAtd2Via2l0LXN5 c3RlbS1mb250LCBIZWx2ZXRpY2EgTmV1ZSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmOyBjb2xvcjpy Z2JhKDAsIDAsIDAsIDEuMCk7IiBjbGFzcz0iIj48YiBjbGFzcz0iIj5Gcm9tOg0KPC9iPjwvc3Bh bj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IC13ZWJraXQtc3lzdGVtLWZvbnQsIEhlbHZldGlj YSBOZXVlLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IiBjbGFzcz0iIj48YSBocmVmPSJtYWlsdG86 aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIiBjbGFzcz0iIj5pbnRlcm5ldC1kcmFmdHNAaWV0Zi5v cmc8L2E+PGJyIGNsYXNzPSIiPg0KPC9zcGFuPjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLXRv cDogMHB4OyBtYXJnaW4tcmlnaHQ6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBtYXJnaW4tbGVm dDogMHB4OyIgY2xhc3M9IiI+DQo8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IC13ZWJraXQtc3lz dGVtLWZvbnQsIEhlbHZldGljYSBOZXVlLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IGNvbG9yOnJn YmEoMCwgMCwgMCwgMS4wKTsiIGNsYXNzPSIiPjxiIGNsYXNzPSIiPlN1YmplY3Q6DQo8L2I+PC9z cGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogLXdlYmtpdC1zeXN0ZW0tZm9udCwgSGVsdmV0 aWNhIE5ldWUsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsiIGNsYXNzPSIiPjxiIGNsYXNzPSIiPkkt RCBBY3Rpb246IGRyYWZ0LXNoZW4taXNpcy1nZW8tY29vcmRpbmF0ZXMtMDIudHh0PC9iPjxiciBj bGFzcz0iIj4NCjwvc3Bhbj48L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbi10b3A6IDBweDsgbWFy Z2luLXJpZ2h0OiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgbWFyZ2luLWxlZnQ6IDBweDsiIGNs YXNzPSIiPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiAtd2Via2l0LXN5c3RlbS1mb250LCBI ZWx2ZXRpY2EgTmV1ZSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmOyBjb2xvcjpyZ2JhKDAsIDAsIDAs IDEuMCk7IiBjbGFzcz0iIj48YiBjbGFzcz0iIj5EYXRlOg0KPC9iPjwvc3Bhbj48c3BhbiBzdHls ZT0iZm9udC1mYW1pbHk6IC13ZWJraXQtc3lzdGVtLWZvbnQsIEhlbHZldGljYSBOZXVlLCBIZWx2 ZXRpY2EsIHNhbnMtc2VyaWY7IiBjbGFzcz0iIj5PY3RvYmVyIDI4LCAyMDE2IGF0IDE6NDY6MjYg UE0gUERUPGJyIGNsYXNzPSIiPg0KPC9zcGFuPjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLXRv cDogMHB4OyBtYXJnaW4tcmlnaHQ6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBtYXJnaW4tbGVm dDogMHB4OyIgY2xhc3M9IiI+DQo8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IC13ZWJraXQtc3lz dGVtLWZvbnQsIEhlbHZldGljYSBOZXVlLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IGNvbG9yOnJn YmEoMCwgMCwgMCwgMS4wKTsiIGNsYXNzPSIiPjxiIGNsYXNzPSIiPlRvOg0KPC9iPjwvc3Bhbj48 c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IC13ZWJraXQtc3lzdGVtLWZvbnQsIEhlbHZldGljYSBO ZXVlLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IiBjbGFzcz0iIj4mbHQ7PGEgaHJlZj0ibWFpbHRv OmktZC1hbm5vdW5jZUBpZXRmLm9yZyIgY2xhc3M9IiI+aS1kLWFubm91bmNlQGlldGYub3JnPC9h PiZndDs8YnIgY2xhc3M9IiI+DQo8L3NwYW4+PC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW4tdG9w OiAwcHg7IG1hcmdpbi1yaWdodDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IG1hcmdpbi1sZWZ0 OiAwcHg7IiBjbGFzcz0iIj4NCjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogLXdlYmtpdC1zeXN0 ZW0tZm9udCwgSGVsdmV0aWNhIE5ldWUsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsgY29sb3I6cmdi YSgwLCAwLCAwLCAxLjApOyIgY2xhc3M9IiI+PGIgY2xhc3M9IiI+UmVwbHktVG86DQo8L2I+PC9z cGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogLXdlYmtpdC1zeXN0ZW0tZm9udCwgSGVsdmV0 aWNhIE5ldWUsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsiIGNsYXNzPSIiPjxhIGhyZWY9Im1haWx0 bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmciIGNsYXNzPSIiPmludGVybmV0LWRyYWZ0c0BpZXRm Lm9yZzwvYT48YnIgY2xhc3M9IiI+DQo8L3NwYW4+PC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8ZGl2 IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCkEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJs ZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy48YnIgY2xhc3M9 IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDtUaXRsZSAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs6IENhcnJ5aW5nIEdlbyBDb29yZGluYXRlcyBJ bmZvcm1hdGlvbiBJbiBJUy1JUzxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwO0F1dGhvcnMgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7OiBOYWltaW5nIFNoZW48YnIgY2xhc3M9IiI+DQombmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtFbmtlIENoZW48L2Rpdj4NCjwvYmxvY2txdW90ZT4N CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4mbmJzcDsg Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtBY2VlIExpbmRlbjxiciBjbGFzcz0iIj4NCjxzcGFu IGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPkZp bGVuYW1lICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzogZHJhZnQt c2hlbi1pc2lzLWdlby1jb29yZGluYXRlcy0wMi50eHQ8YnIgY2xhc3M9IiI+DQo8c3BhbiBjbGFz cz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5QYWdlcyAm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDs6IDk8YnIgY2xhc3M9IiI+DQo8c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3 aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5EYXRlICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzogMjAxNi0xMC0yODxiciBjbGFz cz0iIj4NCjxiciBjbGFzcz0iIj4NCkFic3RyYWN0OjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNw O1RoaXMgZG9jdW1lbnQgZGVmaW5lcyBhIG5ldyBJUy1JUyBUTFYgd2hpY2ggY2FycmllcyB0aGUg R2VvPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Q29vcmRpbmF0ZXMgaW5mb3JtYXRpb24gb2Yg dGhlIHN5c3RlbS4gJm5ic3A7VGhlIEdlbyBDb29yZGluYXRlczxiciBjbGFzcz0iIj4NCiZuYnNw OyZuYnNwO2luZm9ybWF0aW9uIGNhbiBiZSB1c2VkIGJ5IElTLUlTIHJvdXRpbmcgb3IgYnkgYW55 IGFwcGxpY2F0aW9ucy48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+ DQpUaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFmdCBpczo8YnIg Y2xhc3M9IiI+DQo8YSBocmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFm dC1zaGVuLWlzaXMtZ2VvLWNvb3JkaW5hdGVzLyIgY2xhc3M9IiI+aHR0cHM6Ly9kYXRhdHJhY2tl ci5pZXRmLm9yZy9kb2MvZHJhZnQtc2hlbi1pc2lzLWdlby1jb29yZGluYXRlcy88L2E+PGJyIGNs YXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KVGhlcmUncyBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBh dmFpbGFibGUgYXQ6PGJyIGNsYXNzPSIiPg0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry YWZ0LXNoZW4taXNpcy1nZW8tY29vcmRpbmF0ZXMtMDI8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9 IiI+DQpBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6PGJy IGNsYXNzPSIiPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LXNoZW4t aXNpcy1nZW8tY29vcmRpbmF0ZXMtMDI8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIg Y2xhc3M9IiI+DQpQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0 ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uPGJyIGNsYXNzPSIiPg0KdW50aWwgdGhlIGh0 bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy48 YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZh aWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6PGJyIGNsYXNzPSIiPg0KZnRwOi8vZnRwLmlldGYu b3JnL2ludGVybmV0LWRyYWZ0cy88YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpfX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxiciBjbGFzcz0iIj4NCkkt RC1Bbm5vdW5jZSBtYWlsaW5nIGxpc3Q8YnIgY2xhc3M9IiI+DQpJLUQtQW5ub3VuY2VAaWV0Zi5v cmc8YnIgY2xhc3M9IiI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2kt ZC1hbm5vdW5jZTxiciBjbGFzcz0iIj4NCkludGVybmV0LURyYWZ0IGRpcmVjdG9yaWVzOiBodHRw Oi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sPGJyIGNsYXNzPSIiPg0Kb3IgZnRwOi8vZnRwLmll dGYub3JnL2lldGYvMXNoYWRvdy1zaXRlcy50eHQ8YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjwvYmxv Y2txdW90ZT4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+ DQo= --_000_4156A7366F7D4577BBFF527C185DD238ciscocom_-- From nobody Sun Oct 30 11:48:47 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A160D129482; Sun, 30 Oct 2016 11:48:45 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147785332565.20604.18023774216728139239.idtracker@ietfa.amsl.com> Date: Sun, 30 Oct 2016 11:48:45 -0700 Archived-At: Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-09.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2016 18:48:45 -0000 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 of the IETF. Title : IS-IS Extensions for Segment Routing Authors : Stefano Previdi Clarence Filsfils Ahmed Bashandy Hannes Gredler Stephane Litkowski Bruno Decraene Jeff Tantsura Filename : draft-ietf-isis-segment-routing-extensions-09.txt Pages : 41 Date : 2016-10-30 Abstract: Segment Routing (SR) allows for a flexible definition of end-to-end paths within IGP topologies by encoding paths as sequences of topological sub-paths, called "segments". These segments are advertised by the link-state routing protocols (IS-IS and OSPF). This draft describes the necessary IS-IS extensions that need to be introduced for Segment Routing. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-segment-routing-extensions-09 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Oct 30 11:55:18 2016 Return-Path: X-Original-To: isis-wg@ietfa.amsl.com Delivered-To: isis-wg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C76A51294F3 for ; Sun, 30 Oct 2016 11:55:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.018 X-Spam-Level: X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, 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 nAqxepB9NADj for ; Sun, 30 Oct 2016 11:55:15 -0700 (PDT) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E3D71294B8 for ; Sun, 30 Oct 2016 11:55:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2215; q=dns/txt; s=iport; t=1477853715; x=1479063315; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=mtDBaN3QUsXMBDn9U9t/x6fnmQ5aLrsTaAu0DQuE7ZI=; b=EEFD/5Uszu3t2li4gBohW6NmnkjXCiIAuqzMdfvwwHByG/Gdmn/jJpwk 7JKdw95rZkbU4E7M9mqaT9ySQW8Sa3mt/NP30c4VzEbaGPhYO7kP2+i0T mbSgmNjuXCZkl6cgM3Xm2s7MKvaX3MJc3ClXjW7i/E7zwKt0bi3tFovWN I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BwAQD1QBZY/4oNJK1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgyoBAQEBAR9YfQeNL5Z+lD6CBx0NhXkCggE/FAECAQEBAQEBAWIohGI?= =?us-ascii?q?BAQEDAQEBATc0EAsCAQgYHhAnCyUCBBOITAgOvyIBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEchj2BfYJYhEeDMYIvBZoYAYYvigCBbk6EH4kpjRGEAQEeNmCFEnKGQ4E?= =?us-ascii?q?JAQEB?= X-IronPort-AV: E=Sophos;i="5.31,423,1473120000"; d="scan'208";a="163628241" Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 30 Oct 2016 18:55:14 +0000 Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u9UItEiq007652 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Sun, 30 Oct 2016 18:55:14 GMT Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-010.cisco.com (64.101.220.150) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 30 Oct 2016 14:55:13 -0400 Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Sun, 30 Oct 2016 14:55:13 -0400 From: "Stefano Previdi (sprevidi)" To: "isis-wg@ietf.org list" Thread-Topic: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-09.txt Thread-Index: AQHSMt8l21c5oqYZ6UmEPWDr+Vud7Q== Date: Sun, 30 Oct 2016 18:55:13 +0000 Message-ID: <9E4BBF6E-2EF7-4D1F-97AA-B4215AD557B8@cisco.com> References: <147785332565.20604.18023774216728139239.idtracker@ietfa.amsl.com> In-Reply-To: <147785332565.20604.18023774216728139239.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.61.73.13] Content-Type: text/plain; charset="us-ascii" Content-ID: <375237ACADC3EF44839B895DF9391A62@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-09.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2016 18:55:17 -0000 All, this version added the SRMS Preference sub-TLV and defines the behavior in = case of multiple occurrences of SR-Capability, SRLB and SRMS Preference sub= -TLVs are received. Thanks. s. > On Oct 30, 2016, at 7:48 PM, internet-drafts@ietf.org wrote: >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the IS-IS for IP Internets of the IETF. >=20 > Title : IS-IS Extensions for Segment Routing > Authors : Stefano Previdi > Clarence Filsfils > Ahmed Bashandy > Hannes Gredler > Stephane Litkowski > Bruno Decraene > Jeff Tantsura > Filename : draft-ietf-isis-segment-routing-extensions-09.txt > Pages : 41 > Date : 2016-10-30 >=20 > Abstract: > Segment Routing (SR) allows for a flexible definition of end-to-end > paths within IGP topologies by encoding paths as sequences of > topological sub-paths, called "segments". These segments are > advertised by the link-state routing protocols (IS-IS and OSPF). >=20 > This draft describes the necessary IS-IS extensions that need to be > introduced for Segment Routing. >=20 >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensio= ns/ >=20 > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-09 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-isis-segment-routing-exten= sions-09 >=20 >=20 > Please note that it may take a couple of minutes from the time of submiss= ion > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www.ietf.org/mailman/listinfo/isis-wg From nobody Mon Oct 31 09:18:41 2016 Return-Path: X-Original-To: isis-wg@ietf.org Delivered-To: isis-wg@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CD0D41295D1; Mon, 31 Oct 2016 09:18:36 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.36.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147793071683.32374.14772278076234326608.idtracker@ietfa.amsl.com> Date: Mon, 31 Oct 2016 09:18:36 -0700 Archived-At: Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D Action: draft-ietf-isis-auto-conf-03.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.17 List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2016 16:18:37 -0000 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 of the IETF. Title : ISIS Auto-Configuration Authors : Bing Liu Bruno Decraene Ian Farrer Mikael Abrahamsson Les Ginsberg Filename : draft-ietf-isis-auto-conf-03.txt Pages : 15 Date : 2016-10-31 Abstract: This document specifies IS-IS auto-configuration mechanisms. The key components are IS-IS System ID self-generation, duplication detection and duplication resolution. These mechanisms provide limited IS-IS functions, and so are suitable for networks where plug-and-play configuration is expected. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-isis-auto-conf/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-isis-auto-conf-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-auto-conf-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/