Re: [Lsr] Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed draft name)
Dear LSR WG, I object on two basis ... 1) The version -04 does not contain normative MUST that UPA shall only be used to trigger invalidation when end to end encapsulation is used for subject application(s). So as written is in fact quite undeployable in a mixed vendor and legacy node(s) environment doing hop by hop routing. We can't just hope that this is all about configuring the network in a proper way. 2) The solution is too pragmatic ... It does not look at the problem holistically. Yes I still think the problem is worth solving but outside of link state IGP doing UPA blast flooding everywhere domain wide even if no nodes need that info. As discussed at length it could be done via either BGP indirection or via PUB-SUB model (as proposed). Regards, Robert On Wed, Aug 23, 2023 at 10:07 PM Acee Lindem wrote: > LSR Working Group, > > This begins the working group adoption call for “IGP Unreachable Prefix > Announcement” - draft-ppsenak-lsr-igp-unreach-prefix-announce-04. > Please indicate your support or objection on this list prior to September > 7th, 2023. > > Thanks, > Acee > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
Re: [Lsr] Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed draft name)
I object. This solution is a poor way of addressing the issues. My reasons have been discussed to death already. Tony > On Aug 23, 2023, at 1:07 PM, Acee Lindem wrote: > > LSR Working Group, > > This begins the working group adoption call for “IGP Unreachable Prefix > Announcement” - draft-ppsenak-lsr-igp-unreach-prefix-announce-04. > Please indicate your support or objection on this list prior to September > 7th, 2023. > > Thanks, > Acee > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
Re: [Lsr] Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed draft name)
I support WG adoption. The problem is a useful problem to solve and the solution defined in the document has been implemented and proven to work. Les > -Original Message- > From: Lsr On Behalf Of Acee Lindem > Sent: Wednesday, August 23, 2023 1:07 PM > To: lsr > Cc: draft-ppsenak-lsr-igp-ureach-prefix-annou...@ietf.org > Subject: [Lsr] Working Group Adoption of "IGP Unreachable Prefix > Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed > draft name) > > LSR Working Group, > > This begins the working group adoption call for “IGP Unreachable Prefix > Announcement” - draft-ppsenak-lsr-igp-unreach-prefix-announce-04. > Please indicate your support or objection on this list prior to September 7th, > 2023. > > Thanks, > Acee > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
[Lsr] Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed draft name)
LSR Working Group, This begins the working group adoption call for “IGP Unreachable Prefix Announcement” - draft-ppsenak-lsr-igp-unreach-prefix-announce-04. Please indicate your support or objection on this list prior to September 7th, 2023. Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
[Lsr] IPR Poll for Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed draft name and IPR link)
Co-Authors, Are you aware of any IPR that applies to draft-posenak-lsr-igp-ureach-prefix-announce-04? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). There is one IPR statement - https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ppsenak-lsr-igp-ureach-prefix-announce If you are listed as a document author or contributor please respond to this email regardless of whether or not you are aware of any relevant IPR. *The response needs to be sent to the LSR WG mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the LSR WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Also, since there are nine authors, it would be great if you could reduce the author list and make the others contributors (which still requires an IPR response). Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
[Lsr] IPR Poll for Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed draft name)
Co-Authors, Are you aware of any IPR that applies to draft-posenak-lsr-igp-ureach-prefix-announce-04? 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 a few IPR statements already - https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-lsr-dynamic-flooding If you are listed as a document author or contributor please respond to this email regardless of whether or not you are aware of any relevant IPR. *The response needs to be sent to the LSR WG mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the LSR WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Also, since there are nine authors, it would be great if you could reduce the author list and make the others contributors (which still requires an IPR response). Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
[Lsr] Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-unreach-prefix-announce-04
LSR Working Group, This begins the working group adoption call for “IGP Unreachable Prefix Announcement” - draft-ppsenak-lsr-igp-unreach-prefix-announce-04. Please indicate your support or objection on this list prior to September 7th, 2023. Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
[Lsr] IPR Poll for Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-unreach-prefix-announce-04
Co-Authors, Are you aware of any IPR that applies to draft-posenak-lsr-igp-unreach-prefix-announce-04? 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 a few IPR statements already - https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-lsr-dynamic-flooding If you are listed as a document author or contributor please respond to this email regardless of whether or not you are aware of any relevant IPR. *The response needs to be sent to the LSR WG mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the LSR WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Also, since there are nine authors, it would be great if you could reduce the author list and make the others contributors (which still requires an IPR response). Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
Re: [Lsr] WG Last Call for draft-ietf-lsr-ospfv3-extended-lsa-yang
As a co-author, I support the publication of this draft. I'm not aware of any IPR. Thanks, Yingzhen On Fri, Aug 18, 2023 at 5:27 PM Christian Hopps wrote: > > This begins a 2 week WG Last Call, ending Sep 1, 2023, for: > > > https://datatracker.ietf.org/doc/draft-ietf-lsr-ospfv3-extended-lsa-yang/ > > Authors, > > Please indicate to the list, your knowledge of any IPR related to this > work. > > Thanks, > Chris. > > ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
Re: [Lsr] WG Last Call for draft-ietf-lsr-ospfv3-extended-lsa-yang
From: Acee Lindem
Sent: 21 August 2023 15:52
Hi Tom,
Thanks for the review.
> On Aug 21, 2023, at 06:57, tom petch wrote:
>
> From: Lsr on behalf of Christian Hopps
>
> Sent: 19 August 2023 01:26
>
> This begins a 2 week WG Last Call, ending Sep 1, 2023, for:
>
> https://datatracker.ietf.org/doc/draft-ietf-lsr-ospfv3-extended-lsa-yang/
>
>
> Some stray thoughts from a quick look at -22
>
> ** It is an augmentation of the OSPF base model provided support for
> perhaps provides
>
> /ospf:ospfv3/ospf:body:
> I have forgotten what that final colon does but it is not in the YANG
>
> OLD
> | +--ro prefix-options
> | | +--ro prefix-options* identityref
> NEW
> | +--ro prefix-options
> | | +--ro prefix-option* identityref
> might be clearer with the singular
This is a leaf-list of options. One can debate whether it would be cleaner if
it were singular. However, this is moot point as this is from RFC 9129.
Ah yes, I missed that when reviewing ospf-yang
Tom Petch
>
> identity ospfv3-e-inter-area-router-lsa {
> ...
> reference
> "RFC 8362: OSPFv3 Link State Advertisement (LSA)
> Extensibility, Section 4.3";
> Section 4.4 I think
> I have not checked to see which section the data objects relate to
Fixed.
>
> description
> "Intra-Area Prefix TLV Grouping";
> reference
> "RFC 8362: OSPFv3 Link State Advertisement (LSA)
> Extensibility, Section 3.4";
> Section 3.7 I think
> I have not checked to see which section the data objects relate to
Fixed.
>
> reference
> "RFC 8362: OSPFv3 Link State Advertisement (LSA)
>Extensibility, Appendix B - AreaExtendedLSASupport";
> (twice)
> Appendix B is Area Configuration Parameters
Fixed.
Thanks,
Acee
>
> Tom Petch
>
> Authors,
>
> Please indicate to the list, your knowledge of any IPR related to this work.
>
> Thanks,
> Chris.
>
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
