Peter,
You said:
we are not defining any new attributes.
We are allowing an existing link attributes to be used by other applications, including, but not limited to SRTE.
What prevent a node (or an application on the node) receiving the LSA from using the attributes carried by the LSA? If no new attributes are to be added, then why need a new ASLA sub-TLV?
Linda
-----Original Message-----
From: Peter Psenak <ppsenak@xxxxxxxxx>
Sent: Friday, May 29, 2020 5:51 AM
To: Linda Dunbar <linda.dunbar@xxxxxxxxxxxxx>; gen-art@xxxxxxxx
Cc: last-call@xxxxxxxx; lsr@xxxxxxxx; draft-ietf-ospf-te-link-attr-reuse.all@xxxxxxxx
Subject: Re: Genart last call review of draft-ietf-ospf-te-link-attr-reuse-12
From: Peter Psenak <ppsenak@xxxxxxxxx>
Sent: Friday, May 29, 2020 5:51 AM
To: Linda Dunbar <linda.dunbar@xxxxxxxxxxxxx>; gen-art@xxxxxxxx
Cc: last-call@xxxxxxxx; lsr@xxxxxxxx; draft-ietf-ospf-te-link-attr-reuse.all@xxxxxxxx
Subject: Re: Genart last call review of draft-ietf-ospf-te-link-attr-reuse-12
Hi Linda,
On 28/05/2020 19:02, Linda Dunbar via Datatracker wrote:
> Reviewer: Linda Dunbar
> Review result: Not Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed by
> the IESG for the IETF Chair. Please treat these comments just like
> any other last call comments.
>
> For more information, please see the FAQ at
>
>
> Document: draft-ietf-ospf-te-link-attr-reuse-??
> Reviewer: Linda Dunbar
> Review Date: 2020-05-28
> IETF LC End Date: 2020-05-29
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: this document introduces a new link attribute advertisement
> in OSPFv2 and OSPFv3 to address general link properties needed for new
> applications, such as Segment Routing.
>
> Major issues:
> The document has good description on the TLV structure of the
> Application specific Advertisements, but fails to describe what are
> the NEW Link attributes needed by Segment Routing. Page 7 (section 5)
> has a really good description on all the link properties added to OSFP
> (RFC4203, RFC 7308, RFC7471, RFC3630) to achieve TE. I can see Segment
> Routing would need each node to advertise its own SID and the SIDs of
> adjacent nodes. Can't they be encoded (or extended) in OSPF's NODE ID?
we are not defining any new attributes.
We are allowing an existing link attributes to be used by other applications, including, but not limited to SRTE.
thanks,
Peter
>
> Minor issues:
>
> Nits/editorial comments:
>
> Best regards,
>
> Linda Dunbar
>
>
>
>
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
