Changes between Version 9 and Version 10 of IETF99


Ignore:
Timestamp:
28/07/17 20:19:46 (5 years ago)
Author:
samitac.ietf@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IETF99

    v9 v10  
    3434----------
    3535
     36= 6lo =
     37
     386lo WG met on Tuesday  afternoon 2nd session for 2 hours.
     39Document status: New RFCS – RFC 8105 (ipv6-over-dect-ule), RFC 8163 (ipv6-over-lobac)
     40 Dropped since last IETF due to lack of interest from Jupitermesh SDO and no updates of the document: draft-ietf-6lo-mesh-link-establishment
     41
     42WG documents:
     43
     446lowpan-ND related extenions:
     451.https://datatracker.ietf.org/doc/html/draft-ietf-6lo-rfc6775-update ( WGLC deadline terminated, comments received and discussed, new revision will be published for the next step)
     462.https://tools.ietf.org/html/ draft-ietf-6lo-backbone-router ( in progress )
     473. https://tools.ietf.org/html/draft-ietf-6lo-ap-nd ( Under security expert review)
     48
     49Applicability  & usecase:
     50https://datatracker.ietf.org/doc/html/draft-ietf-6lo-use-cases (improved to focus on 6lo applicability and guideline for 6lowpan stack adaptation on a L2-constrained networks)
     51
     52Non-WG documents:
     53draft-lijo-6lo-expiration-time-03 was discussed and requested for adoption.
     54draft-huo-6lo-plc-01 talked about ipv6-over-plc; draft content has been also discussed with ITU-T SG-15.
     55A preliminary draft on wireless body area network was presented by a first timer at IETF: draft-sajjad-6lo-wban-00. The document requires many improvements.
     56
     57Discussion on Fragment Forwarding:
     58
     59draft-thubert-6lo-forwarding-fragments was presented 2nd time to make the WG aware of issues of 6lo packet fragmentation over route-over links such as in RPL topologies.  There were long discussions on forwarding requirements and possible solutions and the decision was to form a design team to further investigate 6lo fragmentation requirements on route-over topologies and come up with one or more possible solutions. The chairs are collecting names for people interested in the fragmentation design team.
     60
     61
     62----------
     63
    3664= DHC =
    3765