Interim SCHC #7 2024

WG info

• Charter
• Documents
• ML

Meeting Information

• Date and Time: May 14th, 2024, 7-8am DST, 4pm CEST
• Agenda: on datatracker
• Meeting material: on datatracker
• Meeting link: Meetecho
• Live Minutes: Note-takers Link
• ical: ICS

Agenda

[16:00] Administrivia [10min]

• Note-Well, Scribes, Agenda Bashing
• WG & documents Status
• Lead by: Chairs

[16:10] Discussion on OAM and Actions [20 min]

• Presenter: Ana Minaburo and Laurent Toutain

[16:30] Set of Rules (SoR) [20 min]

• Presenter: Laurent Toutain

[16:50] AOB [ QS ]

Minutes

[16:00] Administrivia [10min]

• Note-Well, Scribes, Agenda Bashing
• WG & documents Status
• Lead by: Chairs
  PT: Note Well and IPR submission when applied
  PT: Agenda is accepted
  PT: Documents. Nothing new.
  PT: Zero Energy devices new document to be discussed
  PT: SCHC FECs document needs more discussion in the ML

[16:10] Discussion on OAM and Actions [20 min]

• Presenter: Ana Minaburo and Laurent Toutain
  LT: Reminder of OAM draft version, still personal submission
  PT: You need to make some changes and then we go for the approuval
  LT: Need to be rename to ICMPv6 compression because not all the OAM
  features are seen in the document
  LT: We introduce 2 new CDA and 2 MO
  LT: Introduce smtg called Action to be used with ping
  AM: Remove the action general definition from this document to a new
  one
  LT: Ask to the ML if concensus about creating a new document
  AP: There is some concensus to do this features as Action
  AP: Adoption call has been submitted and finished, so the document
  can be published as schc-document
  PT: Once the content is clear then the rename can be done.
  LT: new Title: SCHC for the ICMPv6 protocol
  ToDo: Publish the OAM document with the new title
  ToDo: Create a new document with Actions

[16:30] Set of Rules (SoR) [20 min]

• Presenter: Laurent Toutain
  LT: Open discussion
  LT: Set of Rules to do C/D, F/R and Mngmt
  LT: Mngmt Rules can manage Rules to modify the TV in the Rules
  LT: Need to define how we do this mngmt
  LT: Identification of the Rule is different in each SoR
  LT: Actors: Manufacturer, Device Owner, Provider, Technology
  LT: F/R rules depend on Technology with Profiles
  ER: A problem for cellular technologies with very small bwd, perhaps
  having F/R rules not always activated
  PT: Manufacturer decides which technology will be used and the rules
  depending on the device board
  PT: can also be a default SoR
  AP: The operator can add some Rules with different parameters than
  the ones from Manufacturer
  AM: there is a difference between RuleID and the Rules in the SoR
• Does RuleId is linked to all SoR? => Not today because every Profile
  defines a different size
  PT: SoR is what you get from the Web
  PT: Metadata that comes with the Rules is part of the Context
  PT: SoR is not instantiated
  LT: SoR does not identifies the Device
  LT: Does we include this in the archi document?
  PT: Improve Archi with the SoR variations,the name is not
  necessarily that goes on the air, bacause each technology use its
  own
  LT: SCHC PtP association and each association use a SoR
  PT: The identification of the rules in the SoR is not the same as
  RuleID.
• Naming in the SoR is general
• When instantiated the SoR is negotiated with a number of Rules
• It is not dynamically done by the device
• But some Cases that will be used the SoR will use a RuleID number

[16:50] AOB [ QS ]