+------------------------------------------------------------------------------------+ \| IETF 115 - ROLL Meeting \| \| \| \| 15:00 - 16:00 UTC - Tuesday Session III - 8th Nov \| \| \| \| Material: https://datatracker.ietf.org/meeting/115/materials/ \| \| \| \| Notes: https://notes.ietf.org/notes-ietf-115-roll \| \| \| +----------------+----------+---------------------------------------+----------------+ \| Time (UTC) \| Duration \| Draft/Topic \| Presenter \| +----------------+----------+---------------------------------------+----------------+ \| 15:00 - 15:10 \| 10 min \| Introduction - WG Status \| Ines/Dominique \| +----------------+----------+---------------------------------------+----------------+ \| 15:10 - 15:25 \| 15 min \| Status Document Discussion: \| \| \| \| \| \* AODV-RPL \| \| \| \| \| \* RNFD \| Ines/Dominique \| \| \| \| \* NSA \| \| \| \| \| \* MOPEX,CAPABILIIES \| \| +----------------+----------+---------------------------------------+----------------+ \| 15:25 - 15:40 \| 15 min \| draft-ietf-roll-dao-projection \| Pascal \| +----------------+----------+---------------------------------------+----------------+ \| 15:40 - 15:55 \| 15 min \| draft-ietf-6lo-multicast-registration \| Pascal \| +----------------+----------+---------------------------------------+----------------+ \| 15:55 - 16:00 \| 5 min \| Open Floor \| Everyone \| +----------------+----------+---------------------------------------+----------------+ # Meeting notes (times in UTC) {#meeting-notes-times-in-utc} ## Summary of action points (to be filled at the end) {#summary-of-action-points-to-be-filled-at-the-end} ACTIONS: * Pascal to check if AODV-RPL -15 addresses his comments * Chairs to set deadline on AODV-RPL work before dropping it. * Michael to shephard the RNFD draft: lead the discussion and resolution of questions. * Ines to cmplete the dao-projection shephard document * chairs to track draft-thubert-6lo-prefix-registration and coordinate with 6lo. Find reviewers. * chairs to plan for virtual interim ## \[15:00\] Introduction (chairs) {#1500-introduction-chairs} * Note Well, scribes * Michael is taking notes and watching jabber/zulip * Ivan is taking notes * agenda no comments on Agenda ## \[15:05\] some details on WG draft status (chairs) {#1505-some-details-on-wg-draft-status-chairs} * Ines : Delay for DAO projection * Dominique: NSA extensions received 40 comments from AD review, authors are working on revised draft. * Ines: AODV-RPL * RPL instance pairing: authors proposed to use a tuple, no comments en the list. Assumed ok. Some Version 15 published on september, the of JS comment related to improve readibility * Action point: see if Pascal's comments are covered by version 15 * BK: improve the protocol * Next step: last call when points are addressed, basically the Pascal review * Michael: need more involvement from authors to speed up, maybe putting a deadline to January 1st would be a good thing. * Ines: yes, we'll put a deadline * Dominique: MOPEX draft to extend the MOP field. Discussion to be completed regarding a few flags. * Ines: RNFD draft * Discussion on algorithm for LBR crash detection/consensus. Many questions open. * Discussion to be continued on the mailing list. * Michael is the document shepherd for this document. ACTION ## \[15:17\] draft-ietf-roll-dao-projection (Pascal) {#1517-draft-ietf-roll-dao-projection-pascal} * For reference, many tutorial slides can be found at the back of Pascal's presentation * Main RPL specification is based on a DV protocol, optimizes for device to root traffic. * To optimize d2d we have two different extreme options: * 1. Going to the MANET world (AODV), or * 1. control by a central traffic-engineering controller (DAO Projection). The controler will setup the path between two devices * based on main non storing DODAG, which provides the root with more detailed knowledge of the network. * a segment (sequence of intermediate storing-mode routers) complements a DODAG. * assumes the controller knows the memory capabilities of storing-mode nodes and will optimize the path * RAW will use this to optimze reliability and energy * -28 covers WGLC issues; clarifies the rules to avoid loop between instances. Better explains two-hop neighbor discovery. * -29 clean up to remove duplicated text and other cosmetic details. * Rahul (in the chat): "the newly updated Section 3.2 in DAO projection for loop avoidance handles the comments I made before. Thanks" * Rahul: The new section goes into details about explicitely stating loop avoidance. I don't have any objection. * Ines will complete the shephard write-up and chairs will submit for publication ## \[15:36\] draft-ietf-6lo-multicast-registration (Pascal) {#1536-draft-ietf-6lo-multicast-registration-pascal} * Pascal: this is mostly work done at 6lo, but has impact here and in RAW. * extends RFC9010 for different type of addresses. * much like 6LoWPAN ND avoids NS/NA broadcasts, we can also do MLD without broadcasts by proactively installing the multi/anycast addresses with 6LoWPAN ND. * Also distribute stub prefixes into RPL. * A new prefix registration extension. * can cover some SNAC WG scenarios * Pascal goes over line of RFCs/drafts on ND in the IoT space. * David Lamparter: Wifi interfaces that are brigeable do not build a mesh * Pascal: indeed. There is mesh under (like 802.11s) and route-over (that RPL does). * multicast registration is expected by WiSUN alliance. Goes over recent changes in the draft. * in particular, changed the A and M 1-bit flags into a 2-bit P field, which allows to use value 3 for prefix registration * P filed would be specified in this doc and assignement of value 3 would be specified in other draft (prefix registration). * But if prefix doc adopted, could be both in same doc to save work for IANA. * Now on draft-thubert-6lo-prefix-registration * Pascal: reminds that 9010 allows a device that does not speak RPL to register at a RPL router, which in turn will distribute address into the RPL network. This is for host addresses. * want to do same for external destination that are prefixes (for stubs). So far, 0LoWPAN ND does not alow for that. * with prefixes, one issue that shows up is how to do DAD (duplication address detection) * not just match/no-match, but comparing ranges. Would eventually allow node to autoconf a prefix. * open question: should this still be an NS with ARO option, or should this in fact be an RS? Or something new? * goes over message sequence diagram (time 52:30 in video) * Adnan: What is the destination address of the NS in the diagram? * Pascal: the link local unicast address of the router the node is registering to. * Alvaro: chairs, could you please track this document, and make sure there's coordination with 6lo, much like for 6lo-multicast-registration? * Chairs: Yes, will do * Chairs: any volunteers to review this draft in ROLL? none heard, will ask on the ML. ## \[15:54\] Open Floor {#1554-open-floor} * Dominique: address the management of RPL router, put to together a RPLv2 specification. * Comments from the room? * Pascal: a copy of the original 6550 document exists in XML v3. Draft has expired but can be retreived. * Adnan: clarify the terminology across different groups: LLN nodes, 6lo nodes, constrained nodes, etc. * Pascal: in fact, not quite the same functions, hence the specific names. RPL router can actually be 6LN and 6LR. These are logical functions in the same node. A 6LN speaks 8505. * Michael: virtual interim * Dominique: will plan for that. ## \[16:01\] meeting adjourns {#1601-meeting-adjourns} * Dominique: Meeting adjourned