Re: AD review of draft-ietf-6man-rpl-option

2011-09-02 Thread Jari Arkko
Jonathan, Please see below. I think we are converging. The main remaining discussion item below is the description of what the border router does. > Here are my comments in more detail: > >> Datagrams being forwarded within a RPL domain MUST include a RPL >> Option. For datagrams sourced with

Re: AD review of draft-ietf-6man-rpl-routing-header

2011-09-02 Thread Jari Arkko
Jonathan, Please see inline. If you agree with what I'm writing here you should just submit a new draft version and we can take it from there. But it might be that on some aspects we need further discussion. links within a RPL domain SHOULD have a MTU of at least 1280 + 40 (outer IP header) +

Document Action: 'Rationale for update to the IPv6 flow label specification' to Informational RFC (draft-ietf-6man-flow-update-07.txt)

2011-09-02 Thread The IESG
The IESG has approved the following document: - 'Rationale for update to the IPv6 flow label specification' (draft-ietf-6man-flow-update-07.txt) as an Informational RFC This document is the product of the IPv6 Maintenance Working Group. The IESG contact persons are Jari Arkko and Ralph Droms.