Re: [Last-Call] [RTG-DIR] Rtgdir last call review of draft-ietf-bfd-unsolicited-09

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 1/18/22, 8:33 AM, "rtg-dir on behalf of Jeffrey Haas" <rtg-dir-bounces@xxxxxxxx on behalf of jhaas@xxxxxxxx> wrote:

    Henning,

    Thank you for your comments on this draft.

    On Fri, Jan 14, 2022 at 04:29:48AM -0800, Henning Rogge via Datatracker wrote:
    > I have two nits with the document...
    > 
    > 1st, I would like a clarification which/how many (all?) security measurements
    > you consider mandatory... if you (as an example) run the protocol in a trusted
    > environment, you might be able to skip authentication... but maybe using the
    > TTL to keep the protocol "linklocal" should still be mandatory.

    I believe these are addressed by core RFC 5880/5881 procedures.

    Authentication is optional.  
    GTSM is required for single hop sessions.  (RFC 5881, Section 5.)

    > 2nd, I would suggest writing out the full name "Bidirectional Forwarding
    > Detection (BFD)" once in the abstract just to make sure nobody confuses the
    > acronym.

    Thanks.  I suspect this comment will also arrive via the RFC Editor.

Yes - I would have thought BFD was well-known but it is not asterisked. Perhaps due to the more common designation...  

https://www.rfc-editor.org/materials/abbrev.expansion.txt

Acee 

    -- Jeff


-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux