[resend, wrong bfd wg address in first attempt ...]
Authors, WG,

thank you for this document. It is clear and well written.
I didn't find any technical comment to make so I've been nit picking :-)
Please find those comments below.

regards,
martin

---
Please check and address the nits:
https://tools.ietf.org/idnits?url=https://tools.ietf.org/id/draft-ietf-bfd-multipoint-14.txt

On that aspect, does this document really update 7880 as the header says? The Introduction only refers to 5880 and it is not clear in the body of the Document what effectively impacts 7880. The only thing I saw is the addition of new session types but that does not require an update in my opinion. Could you clarify?


   i.e. existence of a path between the sender and the receiver.
do you mean "forwarding path"?


Section 2. and Section 3. seem a bit redundant. They both state the same thing but from a different angle. Not critical.


   Although this document describes a single head and a set of tails
   spanned by a single multipoint path, the protocol is capable of
   supporting (and discriminating between) more than one multipoint path
   at both heads and tails.
There is no text to describe how one could achieve that. Wouldn't it be worth adding some?


   Point-to-point sessions, as described in [RFC5880], are of type
   PointToPoint.
Does this really fit in Section 4.2 which looks to be about the mpBFD session model.


   Sessions of type MultipointHead MUST NOT send BFD control packets
   with the State field being set to INIT, and MUST be ignored on
   receipt.
English is not my native language but I wonder if this really says what you want. It seems that "Sessions" is the subject of "MUST be ignored" while I think it's the packets which are the intended subject. So I'd write:
   and those packets MUST be ignored on receipt.


   Because there is no three-way handshake in Multipoint BFD, a newly
   started head (that does not have any previous state information
   available) SHOULD start with bfd.SessionState set to Down and with
   bfd.RequiredMinRxInterval set to zero in the MultipointHead session.

   To shut down a multipoint session a head MUST administratively set
   bfd.SessionState in the MultipointHead session to either Down or
   AdminDown and SHOULD set bfd.RequiredMinRxInterval to zero.  The
In both these paragraphs one could read that the head "SHOULD set bfd.RequiredMinRxInterval to zero" while 4.4.2 says MUST. Clarification needed?

s/M, P bit/M and P bits/
---

Reply via email to