[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-ospf
Subject:    Re: [Lsr] WG adoption call for draft-acee-lsr-ospf-transport-instance-02
From:       "Ketan Talaulikar \(ketant\)" <ketant=40cisco.com () dmarc ! ietf ! org>
Date:       2021-05-24 18:03:03
Message-ID: MW3PR11MB4570C8146F914EFB86636C53C1269 () MW3PR11MB4570 ! namprd11 ! prod ! outlook ! com
[Download RAW message or body]

Hello Authors,

Some post adoption comments/feedback on the draft :

1) RFC6823 for ISIS GenApp allows that top-level TLV to be also advertised in the \
"default instance". Each application is able to specify whether this is allowed or \
not for itself. Any plans to follow the same approach in OSPF?

2) The application specific information may not only be associated with the node. We \
also need the ability to advertise the application specific info associated with the \
link and prefix as well. There was some feedback on this point during the adoption \
call as well with which I concur. How would this be addressed? Via Transport Link and \
Prefix LSAs? Or is each application expect to be bring in the link and prefix \
descriptors under the application TLV in the proposed LSA? IMHO, it would be valuable \
to preserve the granularity of advertisement offered by OSPF via LSAs for this \
use-case as well.

Thanks,
Ketan

-----Original Message-----
From: Lsr <lsr-bounces@ietf.org> On Behalf Of Christian Hopps
Sent: 21 May 2021 20:35
To: Christian Hopps <chopps@chopps.org>
Cc: lsr@ietf.org; lsr-ads@ietf.org; draft-acee-lsr-ospf-transport-instance@ietf.org
Subject: Re: [Lsr] WG adoption call for draft-acee-lsr-ospf-transport-instance-02


The work is adopted, authors please resubmit as:

draft-ietf-lsr-ospf-transport-instance-00

Thanks,
Chris.

Christian Hopps <chopps@chopps.org> writes:

> This begins a 2 week WG adoption call for the following draft:
> 
> https://datatracker.ietf.org/doc/draft-acee-lsr-ospf-transport-instance/
> 
> Please indicate your support or objection by May 16th, 2021.
> 
> Authors, please respond to the list indicating whether you are aware of any IPR \
> that applies to this draft. 
> Historical Note: The original OSPF transport instance document was adopted by the \
> OSPF WG back in 2009, it was last updated in 2014, and then revived as an \
> individual submission to LSR in Sep 2020. :) 
> Thanks,
> Chris.
> 
> _______________________________________________
> 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


[prev in list] [next in list] [prev in thread] [next in thread]