Re: [OSPF] OSPFv2 SR draft
Chris Bowers <cbowers@juniper.net> Wed, 24 August 2016 18:31 UTC
Return-Path: <cbowers@juniper.net>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3133812B024 for <ospf@ietfa.amsl.com>; Wed, 24 Aug 2016 11:31:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level:
X-Spam-Status: No, score=-1.922 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 B_9aVVTjiqzo for <ospf@ietfa.amsl.com>; Wed, 24 Aug 2016 11:31:04 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0119.outbound.protection.outlook.com [104.47.40.119]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 063DC12D595 for <ospf@ietf.org>; Wed, 24 Aug 2016 11:31:03 -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=zTkgdGmBKcdpQpy44xQhcixwHomJSO7CBQ/mIXkR90k=; b=TipPq9rzLmWQruBmnj/peacFWHnJL9Ga0Ky9zK7qRU1F20TGpGboP4rqWWfcOk2Dd1XmU/fqfSdPHdBEeg251B38vr7e+TTs2/i1wfTpLykIuYGRf8NLXLLwg1UjGbr02wH0LrhSipzn85Z2SP+EKZzjqylRrXBIOm9romVfC28=
Received: from MWHPR05MB2829.namprd05.prod.outlook.com (10.168.245.11) by MWHPR05MB2831.namprd05.prod.outlook.com (10.168.245.13) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.599.2; Wed, 24 Aug 2016 18:31:01 +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.0599.008; Wed, 24 Aug 2016 18:31:02 +0000
From: Chris Bowers <cbowers@juniper.net>
To: Peter Psenak <ppsenak@cisco.com>, OSPF List <ospf@ietf.org>
Thread-Topic: [OSPF] OSPFv2 SR draft
Thread-Index: AQHR4/NCxEmNaMtLk0SvZpHsNgIxfaA3X9HwgBKrwoCAAa8XgIAAG8AAgAUj0SCAA8xkgIAD23gg
Date: Wed, 24 Aug 2016 18:31:02 +0000
Message-ID: <MWHPR05MB282945C376A970F2711059BCA9EA0@MWHPR05MB2829.namprd05.prod.outlook.com>
References: <5791D96B.6080907@cisco.com> <MWHPR05MB2829B34A5B8AB2F4489DC2AFA9060@MWHPR05MB2829.namprd05.prod.outlook.com> <57B1AA09.3070008@cisco.com> <MWHPR05MB28296BF24F47EB6889CEE186A9130@MWHPR05MB2829.namprd05.prod.outlook.com> <57B32AF0.5060300@cisco.com> <MWHPR05MB2829450CD2E99F6996A10A44A9160@MWHPR05MB2829.namprd05.prod.outlook.com> <57BAAA6D.1070905@cisco.com>
In-Reply-To: <57BAAA6D.1070905@cisco.com>
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: ea7a085b-2205-47b9-a3bd-08d3cc4ccd89
x-microsoft-exchange-diagnostics: 1; MWHPR05MB2831; 6:xzvZoTFYFuywlOkKON0HXF8nrCYQ5NgVDvSYLXtqTre2ogaoeVuH23i8oQnXs9xWkRRu3gmRI7eBHL7H+7BjKdlpAqIpkRr28h8dxlqS3BvyBMIM0nwprf1ontb5kBalkpOpEoKXPYypdsvrz3jUw2IV9+6Bxt82mn4VFUbhuBBBi/HKJCTSJUmyb/dJ4CyriOzGVQSusPyFtfeBHWi8i1UZmzK+mpDM64isu/iWYKA42rSHUOP7cz04Ucfgwc1sVI0gKm3H/CYjTl3XusCT96Zj8HjhF1ZamXS7TreyKmnwUCkDKGyEdPx2yreC4pMsSPtz4AJQ1EuuBuKziTMGSQ==; 5:kCEKlDRk/3L5+gejPZZLzEkYQn8aIc+A/A6kLiIXsrAQNGyn4j2d9aHfqB53q1D4SLiYuO7X4HkSQ/qjhK7YbYcgXcWYjndoI99XTP2tv4S5AG6HSjdk3UFGP3iwAFE+D6y/252mO8DTbpEVc2yLJg==; 24:rwCOcoZYAH6ReLlPZRC0OlFKKY5T4tA72UbrB9eMQfgiPxGrTr4aY69bzg66A4Lp9BbMvXpESfXLeKHIlENvAxshLfAFUTocLA0qHySFa2o=; 7:VgWPM87iZprs2AGQCH51UamCHNSv74Y5crst8Cbm9/2VI2jpmw/j7PCg6bEbl/cPxOkxomGuEELxPRng0zWLqEVV68GRj9no68WxSOD859uAhsYf1Udg5ASAi1Ystqc5LxWETfTzX4nibk/WgpK2bXx5pnL5U2ZfLN1R6QNmnyQtWOi0QTiArlPxDLcUWfFIVsVkFSoIPtdNmM97R9cN+3oJFinlM+tgThCovA4neItWcGXdjF8YNAW8c+5NAoJs
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:MWHPR05MB2831;
x-microsoft-antispam-prvs: <MWHPR05MB28313E163FDE2924F391B966A9EA0@MWHPR05MB2831.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(138986009662008)(95692535739014);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026); SRVR:MWHPR05MB2831; BCL:0; PCL:0; RULEID:; SRVR:MWHPR05MB2831;
x-forefront-prvs: 0044C17179
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(189002)(199003)(53754006)(377454003)(24454002)(13464003)(81166006)(99286002)(8676002)(81156014)(10400500002)(106116001)(97736004)(77096005)(8936002)(66066001)(15975445007)(5001770100001)(5002640100001)(105586002)(9686002)(19580405001)(19580395003)(5660300001)(7846002)(3660700001)(101416001)(92566002)(68736007)(33656002)(76576001)(107886002)(87936001)(189998001)(102836003)(7696003)(6116002)(106356001)(86362001)(586003)(7736002)(3846002)(54356999)(74316002)(2900100001)(305945005)(2950100001)(93886004)(2906002)(3280700002)(76176999)(122556002)(50986999); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR05MB2831; 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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Aug 2016 18:31:02.6171 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR05MB2831
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/hM2oTC58s7lfN0pgRLIv0TLzqHY>
Subject: Re: [OSPF] OSPFv2 SR draft
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 18:31:06 -0000
Peter, The text that you propose corresponds to part of the text that I proposed, and it seems good to me. However, the last sentence of the text that I proposed in not addressed. ------ If router B does not advertise the SR-Algorithm TLV for algorithm X, then other routers should not forward traffic destined for a prefix-SID for algorithm X advertised by some router D using a path that would require router B to forward traffic using algorithm X. ------ Is this an oversight? Thanks, Chris -----Original Message----- From: Peter Psenak [mailto:ppsenak@cisco.com] Sent: Monday, August 22, 2016 2:32 AM To: Chris Bowers <cbowers@juniper.net>; OSPF List <ospf@ietf.org> Subject: Re: [OSPF] OSPFv2 SR draft Chris, what about this to be added in the Section 3.1: "A router receiving a Prefix-SID (defined in section 5) from a remote node and with an SR algorithm value that such remote node has not advertised in the SR-Algorithm sub-TLV MUST ignore the Prefix-SID sub-TLV." thanks, Peter On 19/08/16 23:33 , Chris Bowers wrote: > Peter, > > Please share the updated text that you plan to use with the WG, since this is a reasonably significant clarification. > > Thanks, > Chris > > -----Original Message----- > From: Peter Psenak [mailto:ppsenak@cisco.com] > Sent: Tuesday, August 16, 2016 10:02 AM > To: Chris Bowers <cbowers@juniper.net>; OSPF List <ospf@ietf.org> > Subject: Re: [OSPF] OSPFv2 SR draft > > Hi Chris, > > I'll update the draft along those lines. > > thanks, > Peter > > > On 16/08/16 16:02 , Chris Bowers wrote: >> Peter, >> >> I suggest changing the paragraph to read as below to make this clearer. >> >> ===== >> The SR-Algorithm Sub-TLV is optional. It MAY only be advertised once >> in the Router Information Opaque LSA. If the SID/Label Range TLV, as >> defined in Section 3.2, is advertised, then the SR-Algorithm TLV MUST >> also be advertised. If a router C advertises a Prefix-SID sub-TLV for algorithm X >> but does not advertise the SR-Algorithm Sub-TLV with algorithm X, then >> a router receiving that advertisement MUST ignore the Prefix-SID >> advertisement from router C. If router B does not advertise the >> SR-Algorithm TLV for algorithm X, then other routers should not >> forward traffic destined for a prefix-SID for algorithm X advertised by >> some router D using a path that would require router B to forward traffic using >> algorithm X. >> ===== >> >> Thanks, >> Chris >> >> >> >> -----Original Message----- >> From: Peter Psenak [mailto:ppsenak@cisco.com] >> Sent: Monday, August 15, 2016 6:40 AM >> To: Chris Bowers <cbowers@juniper.net>; OSPF List <ospf@ietf.org> >> Subject: Re: [OSPF] OSPFv2 SR draft >> >> Hi Chris, >> >> sorry for the delay, I was on PTO during last two weeks. >> Please see inline: >> >> On 03/08/16 16:45 , Chris Bowers wrote: >>> Peter, >>> >>> Taking a looking at the whole paragraph into this sentence was >>> added, I am not sure how to interpret it. >>> >>> The SR-Algorithm Sub-TLV is optional. It MAY only be advertised once >>> in the Router Information Opaque LSA. If the SID/Label Range TLV, as >>> defined in Section 3.2, is advertised, then the SR-Algorithm TLV MUST >>> also be advertised. If the SR-Algorithm TLV is not advertised by the >>> node, such node is considered as not being segment routing capable. >>> >>> Is this sentence intended to imply that if a router does not >>> advertise the SR-Algorithm TLV including algorithm X, then any >>> prefix-SIDs for algorithm X advertised by that router will be ignored by other routers? >> >> in OSPF we do not have the SR capability TLV. We use SR-Algorithm TLV >> for that purpose. So if a router does not advertise the SR-Algorithm >> TLV for algorithm X, other routers should not send any SR traffic >> using SIDs that were advertised for algorithm X. >> >> If the router does not advertise any SR Algorithm TLV, then the node >> is not SR capable and no SR traffic should be forwarded to such a node. >> >> thanks, >> Peter >> >> >>> >>> If this is the intention, then it would be better to state is more explicitly. >>> >>> If not, then the intended meaning should be clarified. >>> >>> Thanks, >>> Chris >>> >>> >>> -----Original Message----- >>> From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Peter Psenak >>> Sent: Friday, July 22, 2016 3:30 AM >>> To: OSPF List <ospf@ietf.org> >>> Subject: [OSPF] OSPFv2 SR draft >>> >>> Hi All, >>> >>> following text has been added in the latest revision of the OSPFv2 >>> SR draft, section 3.1. >>> >>> "If the SR-Algorithm TLV is not advertised by node, such node is >>> considered as not being segment routing capable." >>> >>> Please let us know if there are any concerns regarding this addition. >>> >>> thanks, >>> Peter >>> >>> _______________________________________________ >>> OSPF mailing list >>> OSPF@ietf.org >>> https://www.ietf.org/mailman/listinfo/ospf >>> . >>> >> >> . >> > > . >
- Re: [OSPF] OSPFv2 SR draft Chris Bowers
- Re: [OSPF] OSPFv2 SR draft Peter Psenak
- Re: [OSPF] OSPFv2 SR draft Chris Bowers
- Re: [OSPF] OSPFv2 SR draft Peter Psenak
- Re: [OSPF] OSPFv2 SR draft Chris Bowers
- [OSPF] OSPFv2 SR draft Peter Psenak
- Re: [OSPF] OSPFv2 SR draft Peter Psenak
- Re: [OSPF] OSPFv2 SR draft Chris Bowers
- Re: [OSPF] OSPFv2 SR draft Peter Psenak
- Re: [OSPF] OSPFv2 SR draft Les Ginsberg (ginsberg)
- Re: [OSPF] OSPFv2 SR draft Chris Bowers
- Re: [OSPF] OSPFv2 SR draft Acee Lindem (acee)
- Re: [OSPF] OSPFv2 SR draft Chris Bowers
- Re: [OSPF] OSPFv2 SR draft Acee Lindem
- Re: [OSPF] OSPFv2 SR draft Chris Bowers