[straw] WGLC Comments on draft-ietf-straw-b2bua-loop-detection-02

["Hutton, Andrew" <[e-mail]>]

I have a couple of comments.

1. Section 4 states " It is RECOMMENDED that B2BUAs implement the loop-detection mechanism for the Via header field, as defined for a Proxy in [RFC5393]."

This could be changed to a MUST requirement by changing it to "B2BUAs MUST implement the updates to [RFC3261] for strengthening the requirements to perform loop detection as specified in [RFC5393]".  I prefer this because it enforces the requirement that some form of loop-detection must be in place when forking.

 
2. Section 5 states " B2BUAs MAY perform the same actions for in-dialog requests, but doing so may cause issues with devices that set Max-Forwards values based upon the number of received Via or Record-Route headers"

I think this could do with some more explanation regarding mid-dialog requests and the issues associated with setting Max-Forwards based on Via or Record-Route. It would be good to remove this "MAY" and have clear requirements for handling mid-dialog requests. Do we really need to have the text about setting based on the number of via or record-route headers?


Regards
Andy