Re: [OSPF] OSPFv2 SR draft
Chris Bowers <cbowers@juniper.net> Fri, 19 August 2016 21:34 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 CE36612B076 for <ospf@ietfa.amsl.com>; Fri, 19 Aug 2016 14:34:00 -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 04W193nQlftm for <ospf@ietfa.amsl.com>; Fri, 19 Aug 2016 14:33:58 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0105.outbound.protection.outlook.com [104.47.40.105]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E043612B039 for <ospf@ietf.org>; Fri, 19 Aug 2016 14:33:57 -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=8LcMnWEitdDpSFaXOrqGUbRJsbBbgTkOwgBsPCJigLk=; b=EKF/Pw6hftg3i57aTuMyg1yL9Mtpc6FI1iesepsQV8ET6ivaiAl9TEBdMMSzcHs994HoMLX3mo2korUt4yK6IYuewkmJNAc/S2te0OueIZRYVdmCu71FrTKuoyleJ1al05eOiK/MYXPVNedsr6CVExAg3IWrf3dxb8Wwm5ZT410=
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_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.1.599.2; Fri, 19 Aug 2016 21:33:55 +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.003; Fri, 19 Aug 2016 21:33:55 +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/NCxEmNaMtLk0SvZpHsNgIxfaA3X9HwgBKrwoCAAa8XgIAAG8AAgAUj0SA=
Date: Fri, 19 Aug 2016 21:33:55 +0000
Message-ID: <MWHPR05MB2829450CD2E99F6996A10A44A9160@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>
In-Reply-To: <57B32AF0.5060300@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.12]
x-ms-office365-filtering-correlation-id: c40891c7-98ff-480f-a84c-08d3c87885d8
x-microsoft-exchange-diagnostics: 1; MWHPR05MB2832; 6:dOfpWa5jWBIyekMju8fmu4fjxlu6kzRLvqPOwdRA2kVxJFMf13rOP9t9JYBEgLH1KEHyE/rXIre7msTlLMYYuj6cNoP2aLhl0VrPQ2UJ6JwZV3SCcjI3mkjnQz7TkgoKeBc5JrY3ip5sicScWf/jlH8/aGEIqTmmKyULE6fe4ByvWnY/5dyeE03JJL1VmmG0YrPs3NxcracEra/DMycVsU5OcCs2euOaNbwPr0Mqgqvnv31iUu7FMdAUFbS3H2vRMwG94i5vkL1oBCc1rciTg6K5UtcsAmeBL4U4FumUAUeUBT7D2BiegBFh/2Ml2bDBqdge2bVX9zakLX7dnyyQMw==; 5:+gBaTGZ5AH8kVsOO2vcAaUArlTUF+Ei+qfQGQMdbJq9Q9Mbtd/HqoNY5uhJzDtHDr+Rqc3Dkggj3AhBb7SKkWFVqypoq0RwSu6d1aluNsdlg9OrXaD5BH9F5qnFzIA5asktK9m9kb4CAoi4b2gxhkw==; 24:vLj40WX16ppIWkAgkvBGBugaFDaD1+YOEqFJI8jgjliSGxvgjKVrxYwxhUHeY/y8dXQveHIb8LPcH8K2jlYx8uG74eGS119WKBxto8TQP70=; 7:t/3Ngqs1XBp/SJ7jcyOl7B3xF+ThaEw0BrYAxbwRPtKQJW7rKbR1Lowsd/8DsvRmEBHAtTsz0JBUSCjRkPptsRDdMR/SW+uUEPu6JgGtulaqOWCsgbmpyTfFUT458ArKHB25mUSzp4SOaZc+DRIELYbJjwUAi8UGhNQTazwZqL3ULlkXQKhkIoSS/FcbO6q6u8drpnVru7o9BVHqlRsJW2MR5/87xySLWAQWHoSlw1is3+aKYhEh8lmcx7li3Nfc
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:MWHPR05MB2832;
x-microsoft-antispam-prvs: <MWHPR05MB2832789F345BE77E2A008776A9160@MWHPR05MB2832.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:MWHPR05MB2832; BCL:0; PCL:0; RULEID:; SRVR:MWHPR05MB2832;
x-forefront-prvs: 0039C6E5C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(189002)(377454003)(53754006)(199003)(24454002)(13464003)(105586002)(106116001)(74316002)(54356999)(122556002)(76176999)(7736002)(7846002)(7696003)(99286002)(305945005)(9686002)(66066001)(76576001)(8676002)(3660700001)(5660300001)(50986999)(81156014)(81166006)(33656002)(19580395003)(87936001)(8936002)(68736007)(86362001)(101416001)(189998001)(106356001)(10400500002)(107886002)(2900100001)(92566002)(586003)(3846002)(2950100001)(93886004)(6116002)(15975445007)(11100500001)(5001770100001)(97736004)(2906002)(77096005)(3280700002)(5002640100001)(19580405001)(102836003); 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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Aug 2016 21:33:55.5570 (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: <https://mailarchive.ietf.org/arch/msg/ospf/uuuXBfG447IttZKZXoQPBdcrhls>
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: Fri, 19 Aug 2016 21:34:01 -0000
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