Re: [Lsr] 答复: 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

Hi Acee, Ketan and Aijun, I also agree that the introduction of source router ID could be a generic useful extension to OSPF, we already have this in IS-IS [RFC 7794]. As for the inter-area topology retrieval use case, I tend to agree that there can be multiple ways to achieve this, thus it w

Re: [Lsr] 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

pretty obvious +1 here --- tony On Tue, Jul 24, 2018 at 3:41 AM Rob Shakir wrote: > +1 to Peter. We should not define fragile solutions within the IETF. > > There are also a multitude of other solutions here already: > > 1) IGP adjacency with one router in each area (at a minimum - probably two

Re: [Lsr] I-D Action: draft-ietf-ospf-lls-interface-id-05.txt

Hi authors, I just run idnits against version 05, and there is still a warning: Miscellaneous warnings: == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 k

[Lsr] 答复: 答复: 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

Hi, Rob: If we use BGP-LS to get the underlay topology, we will not consider deployment other methods such as IGP adjacency or LSDB telemetry, although all of them are applicable. If we deploy BGP-LS adjacency with routers in multi-area to get the full multi-area topology, it will be no dif

[Lsr] 答复: 答复: 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

Hi, Peter: Actually, only the unnumbered scenario that you insisted has no straightforward solution for the topology reconstruction. As I had explained previously, unnumbered interface deployment is very seldom within our network, because it is unavailable for remote testing and management. If

[Lsr] I-D Action: draft-ietf-isis-mpls-elc-04.txt

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 the IETF. Title : Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-IS Authors : Xiaohu Xu

[Lsr] 答复: 答复: 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

Hi, Ketan and Acee: I am working on the other use cases of "Source Router ID" extension, which may corresponding to that in RFC7794. Once finished, I will update the draft. RFC5392 and RFC5316 are for inter-AS TE extension, not inter-area scenario and solution that proposed in this draft. -

[Lsr] I-D Action: draft-ietf-ospf-segment-routing-msd-15.txt

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 the IETF. Title : Signaling MSD (Maximum SID Depth) using OSPF Authors : Jeff Tantsura Uma Chundur

Re: [Lsr] I-D Action: draft-ietf-isis-segment-routing-msd-13.txt

Folks, The only update is the correct name for the registry - from "MSD Types" to "IGP MSD Types" Cheers, Jeff On 7/24/18, 15:51, "lsr-boun...@ietf.org on behalf of internet-dra...@ietf.org" wrote: A New Internet-Draft is available from the on-line Internet-Drafts directories.

[Lsr] I-D Action: draft-ietf-isis-segment-routing-msd-13.txt

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 the IETF. Title : Signaling MSD (Maximum SID Depth) using IS-IS Authors : Jeff Tantsura Uma Chundu

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

Hi Acee, According to our logs, although we made individual registrations through the early allocation process, it looks like all of the RFC 7684 registries at https://www.iana.org/assignments/ospfv2-parameters were created in September 2015, after the document was approved by the IESG. Amand

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:

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] [IANA #1117133] Early Allocation Request for "Signaling MSD (Maximum SID Depth) using IS-IS"

Hi Acee, We actually aren't able to create registries through the RFC 7120 early allocation process. We'll have to hold off until the IESG notifies us that they've approved the document for publication. Best regards, Amanda On Tue Jul 24 14:50:47 2018, a...@cisco.com wrote: > Hi Amanda, et al,

[Lsr] IETF 102 LSR Meeting Minutes

All, I have uploaded the meeting minutes - https://datatracker.ietf.org/doc/minutes-102-lsr/ Thanks so much to Yingzhen for taking them. As you can see, we had quite a lively discussion with respect to the flooding optimizations. I intend to start a separate thread as to how we move forward.

Re: [Lsr] 答复: 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

On 23 July 2018 at 23:37, Aijun Wang wrote: > > > *To Rob: * > > > > BGP-LS is one prominent method to get the underlay network topology and > has more flexibility to control the topology export as described in RFC > 7752 . > > > > Solution 1) that y

Re: [Lsr] 答复: 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

Ack and IMHO the reference to this inter-AS use-case should be removed as it is very specific and works in very limited cases as opposed to rfc5392 which presented a proper OSPF solution for this specific problem (rfc5316 does same for IS-IS). Thanks, Ketan -Original Message- From: Ace

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

Hi Les, It does and thanks for the update. Thanks, Ketan -Original Message- From: Les Ginsberg (ginsberg) Sent: 17 July 2018 17:32 To: Les Ginsberg (ginsberg) ; Ketan Talaulikar (ketant) ; Acee Lindem (acee) ; Christian Hopps ; lsr@ietf.org Cc: lsr-cha...@ietf.org; lsr-...@ietf.org Su

[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 consis

Re: [Lsr] 答复: 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

Hi Ketan, On 7/24/18, 7:44 AM, "Ketan Talaulikar (ketant)" wrote: Hi Aijun, Your draft introduces the Source Router ID which is, by itself, an useful protocol extension. I agree. What is the use case for advertisement in IS-IS? Perhaps this could be used as the primary motivati

Re: [Lsr] 答复: 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

Hi Aijun, Your draft introduces the Source Router ID which is, by itself, an useful protocol extension. However, the use-case on inter-as topology retrieval has issues which has been shared by many of us at the mike, offline and on the list. Could you consider de-coupling the two? Also, if the

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

Thanks. We have the BGP-LS work stuck until this is resolved and OSPF/ISIS IANA code points are correctly updated. Would appreciate a fast update to align the language so the draft-ietf-idr-bgp-ls-segment-routing-rld can be progressed in parallel. G/ From: Lsr [mailto:lsr-boun...@ietf.org] On B

Re: [Lsr] 答复: 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

Hi Aijun, On 24/07/18 05:37 , Aijun Wang wrote: _Hi, Peter:_ For point-to-point interface, as described in OSPFv2(RFC2328 12.4.1.1. Describing point-to-point interfaces) , the router LSA will include two links description for each interface, wi