MANET @IETF124

S. Card took these notes. Post-meeting modifications were made by Ronald
in 't Velt

The chairs performed the usual ceremonies. A scheduling conflict with
the TIPTOP working group was noted, which prevented some participants
(e.g., Rick Taylor) from attending.

Ronald in 't Velt reviewed status of two clusters of DLEP extensions
drafts:

Ron listed 3 individual drafts from:

WG poll (very few respondents total) was in favor of adopting
Christopher Dearlove's draft.
The AODVv2 draft, for which implementation status was presented at the
previous IETF, is a large draft and requires more reviews and comments
on the mailing list.
Ron alerted WG to H. Rogge et al "MANET Awareness Model" draft 00
expected by IETF 125.

Daniel Jakubisin & Fred Templin jointly presented
"MANET Internetworking: Problem Statement and Gap Analysis"
Motivating examples involved extending infrastructure network w/MANET.
Another example was interconnecting MANETs via infrastructure for
shorter path.
need 1: MANET unique "local" addresses tolerant of ad hoc
internetworking
need 2: autoconfiguration (2 possible approaches outlined)
need 3: MANET-MANET internetworking using 1 & 2 w/o non-MANET
internetwork protocol
need 4: MANET peer initiates to internetwork correspondent
need 5: internetwork correspondent initiates to MANET peer
need 6: internetwork transit between 2 different MANETs
need 7: "stub MANET to not-so-stubby MANET" (special case of 6?)
WG poll unanimously favored this general topic as being of interest to
WG.
2nd poll w/clarified scope also unanimously favorable WRT interest in
topic.
Ron (chair hat off) explained rationale for his support: too early to
say no. ;-)

Ron presented
"DLEP operational experience & proposed updates, revisited".
This is an update of a presentation by Rick Taylor and Lou Berger in
IETF 110.
Motivations inc. need for work on previously identified issues & heading
off manufacturer consortium divergence from IETF due to ambiguiities in
DLEP RFC 8175.
Ron reviewed many of these ambiguities, concurred that most need
clarification.
Ron identified potential fixes, in some cases w/multiple alternatives,
to several.
The original presentation proposed: (1) errata then (2) update to RFC
8175 (not 8175-bis). Ron (chair hat on) asked the participants what
their thoughts were on the "update" versus "-bis" document question.
Lou Berger explained that an "update" document limits IESG review to
only the changed parts, making the process smoother, whereas a "-bis"
subjects the entire document to potential re-litigation.
Sri Gundavelli suggested maybe it is time for a -bis anyway. It was
mentioned that the working group is contribution-driven, and those
willing to author content should drive the direction.
Ron welcomed additional inputs on the ML.
WG poll unanimously favored doing something re: RFC 8175.
2nd poll yielded only 1 volunteer to co-author text.
There was discussion on strategy, consensus was to let authors get back
to WG.

WG session endded 12:39 meeting local time.