Re: Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019]

Dhruv Dhody <[email protected]>
Newsgroups gmane.ietf.idr
Message-ID <CAB75xn42Yi8Oo9D6gsX+5pXS_8LD9pop-wCq9L2+Z99fTZiBKA@mail.gmail.com>
Hi,

I am late by a day, but since chairs have not yet closed the poll - here I am!

I support adoption for both I-Ds.

Yes to first 3 questions and for the 4th - I have some suggestions
that can be worked on post adoption applicable for both I-Ds:

- Updated requirement language template as per RFC 8174, especially
because you use lowercase normative terms in this document.
- It may good to describe the case where a different path segment at
candidate path and segment list would be useful. Also we should make
it MUST to include both in the SID list rather than SHOULD.
- Extra 'Reserved' in section 3.1 of [1] (not in the figure)
- Remove 'which is a 128-bits value' in section 3.1 of [1] (as so far
you dont specify SRv6 in this I-D)
- We should clarify where is the 'SR Bidirectional Path Sub-TLV' included in.
- Suggested values for IANA, i guess get early IANA allocation post
adoption to avoid issues!
- In figures for sub-TLVs the bit numbering is bit off. Move one space
to the right.
- Can Path segment be part of the segment list (end of the list)?
Should we add some text?
- Can you recheck that a codepoint for the Path Segment sub-tlv
allocated in [1] can be re-used for sub-TLV of SR Segment sub-TLV in
[2]? I ask because usually BGP-LS use different registry.
- s/[I-D.li-idr-sr-policy-path-segment-distribution]/[I-D.li-idr-sr-policy-path-segment]/

Thanks!
Dhruv

[1] https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-segment/
[2] https://tools.ietf.org/html/draft-ietf-idr-te-lsp-distribution-11

On Tue, Sep 17, 2019 at 10:05 PM Susan Hares <[email protected]> wrote:
>
> This begins a 2 week WG Adoption call two related drafts [9/17 to 10/1/2019]
>
> ·         draft-li-bgp-ls-sr-policy-path-segment-03.txt and
>
> ·         draft-li-idr-sr-policy-path-segment-01.txt.
>
>
>
> You can access these two drafts at the following location:
>
>
>
> https://datatracker.ietf.org/doc/draft-li-idr-bgp-ls-sr-policy-path-segment/
>
>
>
> https://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-segment/
>
>
>
> The authors have pointed out that the adoption of this
>
> draft since the following  SR-MPLS Path Segment draft has been adopted:
>
>
>
> https://tools.ietf.org/html/draft-ietf-spring-mpls-path-segment-00
>
>
>
> Please consider the following questions in your responses?
>
>
>
> 1)      Should this SR Policy technology be included in BGP for SR-MPLS
>
>
>
> Spring has adopted the draft, but IDR can provide feedback
>
> to spring about putting this technology in BGP.
>
>
>
> 2)      Is this technology a good way to implement the required
>
> Features in BGP?
>
>
>
> 3)      Is this technology ready for adoption?
>
>
>
> 4)      Do you have any concerns about adopting this technology?
>
>
>
>
>
> Cheers, Susan Hares
>
> _______________________________________________
> Idr mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/idr

_______________________________________________
Idr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/idr
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.