Roman Danyliw has entered the following ballot position for
draft-ietf-lsr-isis-area-proxy-11: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to 
https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-area-proxy/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

** Section 4.3.  Do all the candidates need the Area Proxy System Identifier
TLVs need the same system identifier?

-- Section 4.2 says “For consistency, all Area Leader candidates SHOULD be
configured with the same Proxy System ID, Proxy Hostname, and any other
information that may be inserted into the Proxy LSP.”

-- Section 4.3.1 says: “All candidates advertising the Area Proxy System
Identifier TLV MUST be advertising the same system identifier.”

The first statement suggests that consistency might not always be required, but
the second statement is clear that it always must be the same identifier.

Per our discussion on
https://mailarchive.ietf.org/arch/msg/lsr/HbpEgfX4p7rSMr490kylMyy5pFA, I
believe the agreed resolution is to s/MUST/SHOULD/ in Section 4.3.1.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you to Alexey Melnikov for the SECDIR review.

** Section 8.

8.  Security Considerations

   This document introduces no new security issues.  Security of routing
   within a domain is already addressed as part of the routing protocols
   themselves.  This document proposes no changes to those security
   architectures.

-- What are the relevant pointers to IS-IS security considerations?

Per https://mailarchive.ietf.org/arch/msg/lsr/HbpEgfX4p7rSMr490kylMyy5pFA/,
please consider adding references to RFC 5304 and 5310.



_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to