[Lsr] Flex Algorithm Drafts

The consensus is to adopt the IS-IS and OSPF flexible algorithm drafts in a combined draft, ietf-lsr-sr-flex-algo-00.txt. Authors, please republish the merged draft and I will approve adoption. Thanks, Acee ___ Lsr mailing list Lsr@ietf.org

Re: [Lsr] Working Group Last Call on "Signaling MSD (Maximum SID Depth) using OSPF"

All, Note that a new version, -12, was posted today. Thanks, Acee From: Lsr on behalf of Acee Lindem Date: Tuesday, May 8, 2018 at 11:48 AM To: "lsr@ietf.org" Subject: [Lsr] Working Group Last Call on "Signaling MSD (Maximum SID Depth)

Re: [Lsr] RFC 8379 on OSPF Graceful Link Shutdown

Congrats and Thanks to the Authors! Thanks to Karen Moore for RFC Editorship. Acee On 5/11/18, 8:23 PM, "Lsr on behalf of rfc-edi...@rfc-editor.org" wrote: A new Request for Comments is now available in online RFC libraries.

Re: [Lsr] Working Group Last Call on "Signaling MSD (Maximum SID Depth) using OSPF"

Speaking as a WG member: I have read the document and support publication. Thanks, Acee From: Lsr on behalf of Acee Lindem Date: Thursday, May 10, 2018 at 11:20 AM To: "lsr@ietf.org" Subject: Re: [Lsr] Working Group Last Call on "Signaling

[Lsr] Working Group Last Call on "Signaling MSD (Maximum SID Depth) using OSPF"

We’ve had consensus on the scope and definition of MSD since the Chicago IETF. Since that time, this document has evolved and been improved. It is now ready for Working Group Last Call. Please post your objections or support before 12:00 AM on Wednesday, May 23rd, 2018. For your convenience,

Re: [Lsr] LSR WG Adoption call for "IS-IS Traffic Engineering (TE) Metric Extensions" - draft-ginsberg-lsr-isis-rfc7810bis-00

g (TE) Metric Extensions" - draft-ginsberg-lsr-isis-rfc7810bis-00 WG chairs – It has been more than 2 weeks since adoption call was initiated and support has been expressed on the list – w no objections. Can we consider WG adoption complete? Can I issue a WG version of the draft? Thanx. L

[Lsr] Early Allocation Extension for "IS-IS Extensions for Segment Routing" - draft-ietf-isis-segment-routing-extensions-16.txt

Hi Amanda, et al IANA, Alvaro, For a variety of reasons, we will not finish the subject draft by the end of June when the IANA allocations expire. It has just completed WG last call but there are many fastidious reviewers are in the path to completion. Please extend the allocations and add any

Re: [Lsr] LSR WG Last Call for "Signaling MSD (Maximum SID Depth) using OSPF" - draft-ietf-ospf-segment-routing-msd-10.txt

The WG last call for the subject document has completed. There have been comments from Ketan Talauikar, Chris Hopps, and Tal Mizrahi (Routing Directorate Review). These have been addressed in the -11 and -12 versions and publication will be requested from the -12 version. Thanks, Acee From:

Re: [Lsr] Flex Algo merge work, IS-IS and OSPF FAD sub-TLVs

Hi Peter, Chris, In this particular case, it may be ok as long as we just limit the code point space to the 1 octet type (i.e., 0-255 with reserved values). However, for all the reasons Peter and Les have already articulated, there will be cases where the TLV or Sub-TLV registries cannot be

Re: [Lsr] Flex Algo merge work, IS-IS and OSPF FAD sub-TLVs

May 21, 2018, at 11:11 AM, Acee Lindem (acee) <a...@cisco.com> wrote: > > Hi Peter, Chris, > > In this particular case, it may be ok as long as we just limit the code point space to the 1 octet type (i.e., 0-255 with reserved values). However, for all t

[Lsr] IPR Poll for "OSPFv3 Extensions for Segment Routing" Prior to WG Last Call

Are you aware of any IPR that applies to draft-ietf-ospf-ospfv3-segment-routing-extensions-12.txt? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to

[Lsr] IANA Early Code Point Allocation Request for "OSPFv2 Link Traffic Engineering (TE) Attribute Reuse" - draft-ietf-ospf-te-link-attr-reuse-03.txt

Amanda, et al, Alvaro, Please invoke the early allocation process for IANA code-points requested in the subject draft. Note that the suggested values in Section 10, “IANA Considerations” are out-of-date. Thanks, Acee ___ Lsr mailing list Lsr@ietf.org

Re: [Lsr] Early Allocation Request for "IGP Flexible Algorithm"

t; Hi! This request is fine with me. Acee: yes, according to rfc7120, the AD has to approve early allocation requests for “IETF Review” registries. Right – and the OSPF RI LSA TLV Registry “IETF Review” even if the IS-IS registries are not. Thanks, Acee Alvaro. On May 17, 2018 at 4:15:48 PM,

[Lsr] Flex Algo merge work, IS-IS and OSPF FAD sub-TLVs

Hi Chris, Somehow, I lost the mail below and was only able to retrieve it from the archive. Pardon my top posting. While I believe that sharing code points for values, e.g., IGP Algorithm Type, is a good idea, I don’t necessarily think it is a good idea to merge the TLV type registries. It

Re: [Lsr] [IANA #1109980] Early Allocation Extension for "IS-IS Extensions for Segment Routing" - draft-ietf-isis-segment-routing-extensions-16.txt

Hi Sabrina, Does Alvaro need to approve the allocations or solely the experts? Thanks, Acee On 5/15/18, 5:10 PM, "Lsr on behalf of Sabrina Tanamal via RT" wrote: Hi Acee, We've sent the request below to the

[Lsr] LSR Working Group Last Call for "OSPFv3 Extensions for Segment Routing" - draft-ietf-ospf-ospfv3-segment-routing-extensions-13

This begins an LSR WG last call for the subject draft. Please send your comments to this list prior to 12:00 AM GMT, June 7th, 2018. Thanks, Acee and Chris ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] Working Group Last Call for OSPF LLS Extensions for Local Interface ID Advertisement - draft-ietf-ospf-lls-interface-id-02

, Acee From: Lsr on behalf of "Acee Lindem (acee)" Date: Monday, June 18, 2018 at 12:07 PM To: "lsr@ietf.org" Subject: [Lsr] Working Group Last Call for OSPF LLS Extensions for Local Interface ID Advertisement - draft-ietf-ospf-lls-interface-id-02 This begins

[Lsr] Working Group Last Call for OSPF LLS Extensions for Local Interface ID Advertisement - draft-ietf-ospf-lls-interface-id-02

This begins an LSR WG last call for the subject draft. Please send your comments to this list prior to 12:00 AM GMT, July 3rd, 2018. Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

[Lsr] IETF 102 LSR Working Group Call for Agenda Items

Hi Folks, The LSR (link-state-routing) WG will be meeting on Monday, July 16, 2018 from 9:30 to 12:00 (the first WG slot of IETF 102). Please send us (lsr-cha...@ietf.org) any requests for presentation slots. Thanks, Acee ___ Lsr mailing list

[Lsr] OSPF LLS Extensions for Local Interface ID Advertisement - draft-ietf-ospf-lls-interface-id-02

Authors, LSR WG, This mail is to start the Working Group Last Call IPR poll on the subject document. Are you aware of any IPR that applies to draft-ietf-ospf-lls-interface-id? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more

[Lsr] OSPF LLS Extensions for Local Interface ID Advertisement - draft-ietf-ospf-lls-interface-id-02 (Corrected recipient Email)

Authors, LSR WG, This mail is to start the Working Group Last Call IPR poll on the subject document. Are you aware of any IPR that applies to draft-ietf-ospf-lls-interface-id? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more

Re: [Lsr] WG Last Call for draft-ietf-lsr-isis-rfc7810bis-00

Hi Les, Yes - the Working Group Last call has completed. We'll find a shepherd and request publication. Thanks, Acee On 6/15/18, 10:49 AM, "Les Ginsberg (ginsberg)" wrote: WG chairs - Can we consider WG last call completed? (It has been more than 3 weeks...) Would

Re: [Lsr] RtgDir Early review: draft-ietf-ospf-segment-routing-msd.txt

Hi Jeff, et al, The WG last call has concluded and the version addressing Ketan’s and Tal’s will be submitted for publication. Thanks, Acee From: Jeff Tantsura Date: Monday, April 30, 2018 at 1:38 AM To: Tal Mizrahi Cc:

[Lsr] IPR Poll for "H-bit Support for OSPFv2" - draft-ietf-ospf-ospfv2-hbit-05

Authors, LSR WG, This mail is to start the Working Group Last Call IPR poll on the subject document. Are you aware of any IPR that applies to draft-ietf-ospf-ospfv2-hbit? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more

Re: [Lsr] LSR Working Last Call for draft-ietf-ospf-yang

ot; but it will take me longer to work out if the usage is appropriate. In cases where the leaf should take on a specific identity rather than the general identity, It should simply be derived-from(). I'll revisit these. Thanks, Acee Tom Petch Cheers, Jeff

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

Speaking as WG member: I agree on this and don't believe we need a separate document or a protracted discussion. Additionally, I don't think we should worry about anything going on in other WGs. Thanks, Acee P.S. I'll provide more input to the discussion as well. As luck would have it, I

Re: [Lsr] New Version Notification for draft-wu-lsr-pce-discovery-security-support-00.txt

Hi Qin, On 8/23/18, 11:03 PM, "Qin Wu" wrote: Hi, Folks: draft-wu-pce-discovery-pceps-support-07 has been resubmitted to LSR as draft-wu-lsr-pce-discovery-security-support-00 based on Chairs' suggestion. https://tools.ietf.org/html/draft-wu-lsr-pce-discovery-security-support-00

Re: [Lsr] I-D Action: draft-ietf-ospf-yang-14.txt

This version addresses Tom Petch's last call comments. Thanks, Acee On 8/28/18, 1:10 PM, "Lsr on behalf of internet-dra...@ietf.org" wrote: A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Link State Routing WG of

[Lsr] LSR Working Last Call for draft-ietf-ospf-yang

This begins an LSR WG last call for the subject draft. Please send your comments to this list prior to 12:00 AM GMT, September 8th, 2018. Given the size of the model and the US Labor Day Holiday, we’re allowing a full 3 weeks. For your convenience, here is a URL:

[Lsr] WG Adoption IPR Poll for "Restart Signaling for IS-IS" - draft-ginsberg-isis-rfc5306bis-01

Les, Paul, Are you aware of any IPR that applies to draft-ginsberg-isis-rfc5306bis-01? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this email

Re: [Lsr] I-D Action: draft-ietf-ospf-yang-14.txt

you still have a link-state database in rpc clear-database which I prefer to be Link State Database Tom Petch - Original Message ----- From: "Acee Lindem (acee)" To: Sent: Tuesday, August 28, 2018 6:34 PM > This vers

[Lsr] OSPF/IS-IS Entropy Label Signaling Drafts

Authors of LSR MPLS ELC Signaling Drafts, Now that we have https://www.ietf.org/id/draft-ietf-mpls-spring-entropy-label-12.txt on the RFC queue waiting on a MISREF for Segment Routing MPLS, it seems we should move forward with these drafts. However, it seems that we should advertise an

Re: [Lsr] WG Last Call for draft-ietf-lsr-isis-rfc7810bis-00

fficient that's fine, but it is beyond what I think the draft needs to say. Les > -Original Message- > From: Ketan Talaulikar (ketant) > Sent: Tuesday, July 17, 2018 11:29 AM > To: Les Ginsberg (ginsberg) ; Acee Lindem (acee) > ; Christian Hop

Re: [Lsr] [IANA #1117133] Early Allocation Request for "Signaling MSD (Maximum SID Depth) using IS-IS"

Hi Amanda, It seems to me that we created the RFC 7684 TLV registry via early allocation so that we could allocate code points from other drafts. If this is, in fact, the case, we'll need to manage the IGP MSD Type in the WG. Thanks, Acee On 7/24/18, 4:25 PM, "Amanda Baber via RT" wrote:

[Lsr] IPR Statement for draft-ietf-lsr-isis-rfc7810bis-01

Dear Huawei Director of Licensing, RFC 7810 is being republished to correct an encoding error. Presumably, the IPR statement below would apply since the technical content has not changed: https://datatracker.ietf.org/ipr/2442/ However, it is the policy of IETF to require a separate IPR

[Lsr] IPR Statement for draft-ietf-lsr-isis-rfc7810bis-01

Dear Dan Lang, et al, RFC 7810 is being republished to correct an encoding error. Presumably, the IPR statement below would apply since the technical content has not changed: https://datatracker.ietf.org/ipr/2109/ However, it is the policy of IETF to require a separate IPR statement for BIS

[Lsr] Early Allocation Request for "Signaling MSD (Maximum SID Depth) using IS-IS"

Hi Amanda, et al, Can we get the registry for “IGP MSD Types” created as well? We now have another draft allocating a code point. The IS-IS TLVs have already been allocated through the early allocation process. Hi Authors, Please change “MSD Types” to “IGP MSD Types” in the IANA section

[Lsr] FW: IPR Poll for "H-bit Support for OSPFv2" - draft-ietf-ospf-ospfv2-hbit-05

ase let me know. Otherwise please send your reply to the email thread. Thanks, Yingzhen From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Manish Bhardwaj (manbhard) Sent: Thursday, August 02, 2018 2:35 PM To: Acee Lindem (acee) mailto:a...@cisco.com>>; draft-ietf-ospf-ospfv2-h...@ietf.org

Re: [Lsr] IETF 102 LSR Working Group Call for Agenda Items

stment of IGP Metrics: Drafts: https://datatracker.ietf.org/doc/draft-hu-lsr-network-automatic-optimization/ Presenter: ZhiBo Hu Duration: 15 mins Thanks! ZHiBo From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Acee Lindem (acee) Sent: Monday, June 18, 2018 9:45 PM To: lsr@ietf.org<mailto:lsr

Re: [Lsr] IETF 102 LSR Working Group Call for Agenda Items

[mailto:lsr-boun...@ietf.org] On Behalf Of Acee Lindem (acee) Sent: Monday, June 18, 2018 9:45 PM To: lsr@ietf.org<mailto:lsr@ietf.org> Subject: [Lsr] IETF 102 LSR Working Group Call for Agenda Items Hi Folks, The LSR (link-state-routing) WG will be meeting on Monday, July 16, 2018 from 9:30 to 12

Re: [Lsr] IETF 102 LSR Working Group Call for Agenda Items

ETF 102 LSR Working Group Call for Agenda Items Hi, Request a slot to discuss ISIS extended for PathMTU: Drafts: https://datatracker.ietf.org/doc/draft-hu-lsr-isis-path-mtu/ Presenter: ZhiBo Hu Duration: 10 mins Thanks! ZHiBo From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Acee Lindem (acee) Se

Re: [Lsr] Working Group Last Call for OSPF LLS Extensions for Local Interface ID Advertisement - draft-ietf-ospf-lls-interface-id-02

All, The WG Last Call has completed and we will request publication. Thanks, Acee From: Lsr on behalf of "Acee Lindem (acee)" Date: Monday, June 18, 2018 at 12:07 PM To: "lsr@ietf.org" Subject: [Lsr] Working Group Last Call for OSPF LLS Extensions for Local Interf

Re: [Lsr] [OPSAWG] [GROW] FW: New Version Notification for draft-gu-network-mornitoring-protol-00.txt

> On Jul 6, 2018, at 8:59 AM, Randy Bush wrote: > >> ​Why anyone would need BMP wrapper to monitor IGP ? > > probably similar reasons that folk seem to need bgp-ls to get the > is-is/ospf databases. is-is and ospf have decades of complexity > layered on un-simple bases. so we seek yet

Re: [Lsr] draft-ietf-ospf-lls-interface-id-04 Shepherd review

Hi Peter, The new boiler plate for requirements language, with references to both RFC 2119 and RFC 8174, is: 1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and

Re: [Lsr] draft-ietf-ospf-lls-interface-id-04 Shepherd review

Hi Acee, that is exactly what I have in the draft. thanks, Peter On 09/07/18 13:36 , Acee Lindem (acee) wrote: > Hi Peter, > > The new boiler plate for requirements language, with references to both RFC 2119 and RFC 8174, is: > > >

Re: [Lsr] [GROW] FW: New Version Notification for draft-gu-network-mornitoring-protol-00.txt

ply inline. Best Regards, Robin -Original Message- From: OPSAWG [mailto:opsawg-boun...@ietf.org] On Behalf Of Acee Lindem (acee) Sent: Monday, July 02, 2018 9:24 PM To: Guyunan (Yunan Gu, IP Technology Research Dept. NW) ; g...@ietf.org; ops..

Re: [Lsr] Request slot for LSR@101 - draft-eckert-teas-bier-te-framework

Hi Toerless, Unfortunately, we have a very full agenda already and are not taking additional presentation for IETF 101. Additionally, you're going to need to present it in TEAS anyway due to their mandate... Thanks, Acee On 3/6/18, 4:56 PM, "Lsr on behalf of Toerless Eckert"

Re: [Lsr] advertising tunnels in IGP

Hi Dirk, My memory has faded somewhat on Forwarding Adjacency (FA) implementation. However, since basic MPLS LSPs are unidirectional, doesn’t the SPF two-way check have to be disabled anyway? If so, the Remote Interface ID doesn’t matter. Thanks, Acee From: Lsr on

Re: [Lsr] [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09

Hi Martin, We believe that https://datatracker.ietf.org/doc/draft-ietf-ospf-yang/ satisfies your comments. Please take a look. Thanks, Acee On 12/6/17, 6:46 AM, "Martin Bjorklund" wrote: Ladislav Lhotka wrote: > Reviewer: Ladislav

Re: [Lsr] Yangdoctors last call review of draft-ietf-ospf-yang-09

Hi Lada, We believe that https://datatracker.ietf.org/doc/draft-ietf-ospf-yang/ satisfies your comments. Please take a look ASAP as we intend to WG last called the ietf-ospf YANG model imminently. Thanks, Co-Authors On 12/6/17, 6:26 AM, "Ladislav Lhotka"

Re: [Lsr] FW: New Version Notification for draft-ginsberg-isis-rfc7810bis-00.txt

wrote: Acee, What about ospfv2 vs ospfv3 specifics? We keep it as before - eg “ospf” covers either or ospfv2, “ospfv3” is for ospfv3 only? Regards, Jeff > On Apr 6, 2018, at 12:25, Acee Lindem (acee) <a...@cisco.com> wrote: > > I'

[Lsr] LSR WG Last Call for "Signaling MSD (Maximum SID Depth) using OSPF" - draft-ietf-ospf-segment-routing-msd-10.txt

This begins an LSR WG last call for the subject draft. Please send your comments to this list prior to 12:00 AM GMT, April 20th, 2018. Thanks, Acee and Chris ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

[Lsr] LSR WG IPR Query for "Signaling MSD (Maximum SID Depth) using OSPF" - draft-ietf-ospf-segment-routing-msd-10.txt

Authors, Are you aware of any IPR that applies to draft-ietf-ospf-segment-routing-msd-10.txt? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this

[Lsr] LSR WG IPR Query for "Signaling MSD (Maximum SID Depth) using OSPF" - draft-ietf-ospf-segment-routing-msd-10.txt (one more @#$ time)

Authors, Are you aware of any IPR that applies to draft-ietf-ospf-segment-routing-msd-10.txt? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this

[Lsr] RFC 8362 on OSPFv3 Link State Advertisement (LSA) Extensibility

rfc-edi...@rfc-editor.org Wed, 04 April 2018 04:08 UTCShow header A new Request for Comments is now available in online RFC libraries. RFC 8362 Title: OSPFv3 Link State Advertisement

[Lsr] OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels

Hi Anton, Alvaro, and Mike, In preparation for WG last call, I have a couple comments. 1. Have you considered a shorter name for the RFC? For example: “OSPF Cross Address Family Traffic Engineering Tunnels”? 2. Can you change the requirements language text to the RFC 8174 version? 3.

[Lsr] Flex Algorithms Drafts

In preparation for WG adoption and IANA early code point allocation, I suggest that we rename the “Flexible Algorithm Definition TLV Metric Registry” to the “Flexible Algorithm Definition TLV Metric Type Registry” to avoid confusion as to whether we are defining the actual metrics here. I know

Re: [Lsr] OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels

single protocol, OSPFv2 or OSPFv3 to advertise TE LSAs. Since both IPv4 and IPv6 traffic is tunneled over that LSP, there is no reason to operate both protocols since traffic will take the path of the X-AF LSP - correct? Thanks, Acee --- Anton On 04/04/18 20:13, Acee Lindem (ac

Re: [Lsr] FW: New Version Notification for draft-ginsberg-isis-rfc7810bis-00.txt

?? Les > -Original Message- > From: Acee Lindem (acee) > Sent: Tuesday, April 03, 2018 7:45 AM > To: Les Ginsberg (ginsberg) <ginsb...@cisco.com>; lsr@ietf.org > Subject: Re: [Lsr] FW: New Version Notification for draft-gin

Re: [Lsr] FW: New Version Notification for draft-ginsberg-isis-rfc7810bis-00.txt

". (somewhat verbose) For Category 2 documents "-lsr-" certainly makes sense. Comments?? Les > -Original Message- > From: Acee Lindem (acee) > Sent: Tuesday, April 03, 2018 7:45 AM > To: Les Ginsberg (ginsberg) <ginsb...@cisco.com<mailto:ginsb...@cisco

Re: [Lsr] LSR Working Group Adoption Poll for Flex Algorithm Drafts

Speaking as WG member, I support draft adoption. It was being presented at 2 IETFs and it is one of the more exciting developments in LSR (I’m sure there are other WGs that are feeling insecure based on the power and flexibility of this enhancement ;^). Speaking as WG Co-Chair – I think it

Re: [Lsr] LSR Working Group Adoption Poll for Flex Algorithm Drafts

> Please see inline: > >> -Original Message- >> From: Peter Psenak [mailto:ppse...@cisco.com] >> Sent: Friday, April 20, 2018 3:31 PM >> To: Dongjie (Jimmy) <jie.d...@huawei.com>; Acee Lindem (acee) >> <a...@cisco.com>; lsr@ietf.org &g

Re: [Lsr] OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels

ft one more time? --- Anton On 04/24/18 05:37, Acee Lindem (acee) wrote: > Hi Anton > > Since the IGP shortcut use case you reference does, in fact, use the TED > populated by an instance of one protocol (OSPFv2 or OSPFv3) in an > instanc

[Lsr] LSR Working Group Secretary

All, I’m delighted to announce that Yingzhen Qu has volunteered to take on the role of WG secretary. Yingzhen took the minutes at the first formal meeting of the LSR WG in London and is also RTG WG secretary. Thanks, Acee ___ Lsr mailing list

Re: [Lsr] OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels

e traffic will take the path of the X-AF LSP - correct? But OSPFv2 does not produce IPv6 routes. Both protocols operate in the network: - OSPFv2 computes IPv4 routes and distributes TE database - OSPFv3 computes IPv6 routes. If TE tunnels provide shortcut to destination then OSPFv3 will point

Re: [Lsr] LSR Working Group Adoption Poll for Flex Algorithm Drafts

RE: [Lsr] LSR Working Group Adoption Poll for Flex Algorithm Drafts +1 (I guess you meant :s/LSR/SR ;-) ) Thanks --Bruno From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Acee Lindem (acee) Sent: Tuesday, April 17, 2018 5:24 PM To: lsr@ietf.org Subject: Re: [Lsr] LSR Working Group Adoption Po

Re: [Lsr] [Editorial Errata Reported] RFC7810 (5293)

na <aretana.i...@gmail.com>, "lsr@ietf.org" <lsr@ietf.org>, Olivier Dugeon <olivier.dug...@orange.com> Subject: Re: [Lsr] [Editorial Errata Reported] RFC7810 (5293) Acee, On Mar 22, 2018, at 10:53 AM, Acee Lindem (acee) <a...@cisco.com<mailto:a...@cisco.com>> w

[Lsr] IETF 101 LSR Meeting Minutes

The draft minutes of the IETF 101 LSR Meeting are here: https://datatracker.ietf.org/doc/minutes-101-lsr/ Thanks to Yingzhen Qu for taking them. Please send additions and corrections to the list. Thanks, Acee ___ Lsr mailing list Lsr@ietf.org

Re: [Lsr] FW: New Version Notification for draft-ginsberg-isis-rfc7810bis-00.txt

Hi Les, Can you resubmit as draft-ginsberg-lsr-rfc7810bis-00.txt? Also, please add a "Changes from RFC 7810" section to the "Introduction". I see you have added RFC8174 to the "Requirements Language" section already. I think we should accept this as an LSR Working Group document - does

Re: [Lsr] I-D Action: draft-ietf-ospf-yang-11.txt

All, This version includes remaining YANG doctor comments from Martin as well as RFC references for relevant OSPF, IP FRR, LFA, BFD, and RFCs. There was also one yangdump error fixed. Thanks, Acee On 4/3/18, 3:16 PM, "Lsr on behalf of internet-dra...@ietf.org"

Re: [Lsr] [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09

YANG description or the text specified in te tailf:info YANG extension dependent on the confdc compile options. Thanks, Acee Just my $0.02, r. On Fri, Mar 16, 2018 at 17:31 Acee Lindem (acee) <a...@cisco.com<mailto:a...@cisco.com>> wrote: Hi Martin, On 3/14/18, 3:30 AM, &q

Re: [Lsr] [Editorial Errata Reported] RFC7810 (5293)

Hi Jeff, et al, Speaking as a WG member: I agree there should be an Errata here but the interpretation taken by at least one implementation is to update the length to 5 rather than remove the RESERVED octet. I'd like to hear what other implementations have done. Thanks, Acee On 3/22/18,

Re: [Lsr] LSR WG Adoption call for "IS-IS Traffic Engineering (TE) Metric Extensions" - draft-ginsberg-lsr-isis-rfc7810bis-00

r WG adoption complete? Can I issue a WG version of the draft? Thanx. Les From: Lsr <lsr-boun...@ietf.org> On Behalf Of Acee Lindem (acee) Sent: Monday, April 09, 2018 12:20 PM To: lsr@ietf.org Subject: [Lsr] LSR WG Adoption call for "IS-IS Traffic Engineering (TE) Metric Extensions"

Re: [Lsr] Benjamin Kaduk's No Objection on draft-ietf-ospf-segment-routing-msd-23: (with COMMENT)

Hi Ben, On 10/15/18, 9:58 PM, "Benjamin Kaduk" wrote: Benjamin Kaduk has entered the following ballot position for draft-ietf-ospf-segment-routing-msd-23: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To

[Lsr] OSPF Routing with Cross-Address Family Traffic Engineering Tunnels - draft-ietf-ospf-xaf-te-04.txt

This begins an LSR WG last call for the subject draft. Please send your comments to this list prior to 12:00 AM GMT, November 13th , 2018. While its only an 8 page document, I added an extra week due to the IETF. Please let me know if anyone needs any more time.

Re: [Lsr] LSR Working Last Call for draft-ietf-ospf-yang

The working group last call has completed and all comments have been incorporated. Stephane Litkowski has agreed to be document shepherd. Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] OSPF Routing with Cross-Address Family Traffic Engineering Tunnels - draft-ietf-ospf-xaf-te-04.txt

Speaking as a WG member: I support publication of this draft. All of my comments are already in this revision. Thanks, Acee From: Lsr on behalf of Acee Lindem Date: Monday, October 22, 2018 at 6:25 PM To: "lsr@ietf.org" Subject: [Lsr] OSPF Routing with Cross-Address Family Traffic

[Lsr] OpenFabric

Hey Russ, Aren’t you a WG chair ? If you’re going to continue work on this draft, please rename the file so it shows up in the LSR drafts. If you’re just going to let it expire and descend into obscurity, no action is necessary. Thanks, Acee ___ Lsr

Re: [Lsr] OpenFabric

Sigh! This WG administration note was meant to go to lsr-cha...@ietf.org – not the entire WG…. From: Lsr on behalf of Acee Lindem Date: Thursday, November 1, 2018 at 11:05 AM To: Russ White Cc: "lsr@ietf.org" , Alvaro Retana Subject: [Lsr] OpenFabric Hey Russ,

Re: [Lsr] Opsdir last call review of draft-ietf-ospf-ospfv3-segment-routing-extensions-16

Hi Peter, Joe, et al, On 10/30/18, 8:05 AM, "Peter Psenak (ppsenak)" wrote: Hi Joe, thanks for your review, please see inline (##PP): On 26/10/18 21:42 , Joe Clarke wrote: > Reviewer: Joe Clarke > Review result: Has Nits > > I have been assigned to review

Re: [Lsr] Opsdir last call review of draft-ietf-ospf-ospfv3-segment-routing-extensions-16

Hi Les, On 10/30/18, 11:15 AM, "Les Ginsberg (ginsberg)" wrote: Acee - > > Section 3.2 > > > > "When a router receives multiple overlapping ranges, it MUST > >conform to the procedures defined in > >

[Lsr] IPR Call for draft-ietf-ospf-xaf-te - "OSPF Routing with Cross-Address Family Traffic Engineering Tunnes"

In preparation for requesting publication, I’m making a second IPR call on the subject document. Are you aware of any IPR that applies to draft-ietf-ospf-xaf-te? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). There

Re: [Lsr] Benjamin Kaduk's No Objection on draft-ietf-ospf-lls-interface-id-08: (with COMMENT)

Hi Ben, On 10/25/18, 8:22 AM, "Benjamin Kaduk" wrote: Benjamin Kaduk has entered the following ballot position for draft-ietf-ospf-lls-interface-id-08: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To

[Lsr] IETF 103 Preliminary Agenda

Please see the IETF 103 Preliminary LSR Agenda: https://datatracker.ietf.org/meeting/103/materials/agenda-103-lsr-01 Note that we’re going to need to stick to the agenda so please plan your presentations accordingly. I see some of the presenters on the agenda who are notorious for using all

[Lsr] IPR Call for "YANG Data Model for OSPF Protocol" - draft-ietf-ospf-yang-17

Authors and Contributors, Please confirm that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why? Each author/contributor should respond explicitly to this list. Thanks, Acee

[Lsr] IPR Call for "YANG Data Model for OSPF Protocol" - draft-ietf-ospf-yang-17

Authors and Contributors, Please confirm that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why? Each author/contributor should respond explicitly to this list. Thanks, Acee

Re: [Lsr] Martin Vigoureux's No Objection on draft-ietf-ospf-lls-interface-id-08: (with COMMENT)

Hi Peter, Martin, We can address these comments after the draft is IESG approved and on the RFC Editor queue as long as they don't change the normative specifications. I'm hoping this simple and draft which has an existing implementation will be approved. Thanks, Acee On 10/25/18, 4:54 AM,

Re: [Lsr] RtgDir review: draft-ietf-isis-segment-routing-extensions-20

Hi Russ, Thanks much for the fast turnaround on the review! Les, et al, Go ahead and publish a -21 version to address these comments. I would guess it is going to be awhile until Alvaro gets to this document as he said he was back traveling in next week - better him than me __ Thanks, Acee

Re: [Lsr] WG Adoption Poll for IGP extension for PCEP security capability support in the PCE discovery - draft-wu-lsr-pce-discovery-security-support-00

Speaking as a WG member, I support WG adoption. Thanks, Acee From: Lsr on behalf of Acee Lindem Date: Tuesday, November 13, 2018 at 5:11 PM To: "lsr@ietf.org" Subject: [Lsr] WG Adoption Poll for IGP extension for PCEP security capability support in the PCE discovery -

[Lsr] WG Adoption Poll for IGP extension for PCEP security capability support in the PCE discovery - draft-wu-lsr-pce-discovery-security-support-00

At the LSR WG meeting in Bangkok, there was general agreement that we should adopt this draft given that the PCE WG believes it is useful. Please indicate your support or objection prior to 12:00 AM UT, Wednesday November 26th, 2018. Note the authors may refresh the draft to address some

Re: [Lsr] draft-ietf-ospf-ospfv3-segment-routing-extensions - small change

Hi Peter, I agree - it is not needed in OSPFv3 Extended LSAs. Hi Dirk, Mahendra, How will this impact your implementations? Thanks, Acee On 11/15/18, 9:48 AM, "Lsr on behalf of Peter Psenak (ppsenak)" wrote: Hi, as a part of the RtgDir review we got a comment about the usage

Re: [Lsr] WG Adoption Poll for IGP extension for PCEP security capability support in the PCE discovery - draft-wu-lsr-pce-discovery-security-support-00

pfv2-parameters.xml#ospfv2-parameters-14). Thanks, Julien On 13/11/2018 23:10, Acee Lindem (acee) wrote: > Note the authors may refresh the draft to add

Re: [Lsr] IPR Poll for "IGP extension for PCEP security capability support in the PCE discovery" (Corrected)

Authors – Reminder that you need to explicitly reply to this poll. From: Lsr on behalf of Acee Lindem Date: Wednesday, November 14, 2018 at 3:02 PM To: draft-wu-lsr-pce-discovery-security-support Cc: "lsr@ietf.org" Subject: [Lsr] IPR Poll for "IGP extension for PCEP security capability

Re: [Lsr] WG Adoption Poll for IGP extension for PCEP security capability support in the PCE discovery - draft-wu-lsr-pce-discovery-security-support-00

y name using GENINFO TLV of RFC 6823 3) Carry key name during PCEP session establishment phase instead of discovery phase. -Qin -邮件原件- 发件人: Lsr [mailto:lsr-boun...@ietf.org] 代表 Acee Lindem (acee) 发送时间: 2018年11月15日 23:18 收件人: julien.meu...@orange.com; ls

Re: [Lsr] IPR Poll for "IGP extension for PCEP security capability support in the PCE discovery" (Corrected)

ut I am not sure it is applicable. I will consult with our IPR people to check on this. -Qin 发件人: Acee Lindem (acee) [mailto:a...@cisco.com] 发送时间: 2018年11月16日 11:59 收件人: draft-wu-lsr-pce-discovery-security-support 抄送: lsr@ietf.org; p...@ietf.org 主题: Re: [Lsr] IPR Poll for "IGP exten

[Lsr] IPR Call for "YANG Data Model for OSPF Protocol" - draft-ietf-ospf-yang-17

Authors and Contributors, Please confirm that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why? Each author/contributor should respond explicitly to this list. Thanks, Acee

[Lsr] IPR Call for "YANG Data Model for OSPF Protocol" - draft-ietf-ospf-yang-17

Authors and Contributors, Please confirm that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why? Each author/contributor should respond explicitly to this list. Thanks, Acee

[Lsr] IPR Poll for "IGP extension for PCEP security capability support in the PCE discovery" (Corrected)

Authors, Are you aware of any IPR that applies to draft-wu-lsr-pce-discovery-security-support? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). There are currently no IPR disclosures against

[Lsr] IPR Poll for "IGP extension for PCEP security capability support in the PCE discovery"

Authors, Are you aware of any IPR that applies to draft-wu-lsr-pce-discovery-security-support? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). There are currently no IPR disclosures against ospf-ietf-ospf-ospfv2-hbit.

[Lsr] IPR Call for draft for "Restart Signaling for IS-IS" - draft-ietf-lsr-isis-rfc5306bis

Les, Paul, Mike, In preparation for the requested WG last call, I’d ask again if you are aware of any IPR. Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

  1   2   3   4   5   6   7   8   9   >