[Autoconf] Request to publish draft-ietf-autoconf-manetarch-07.txt

[Shubhranshu <[e-mail]>]

This is a request to publish draft-ietf-autoconf-manetarch-07.txt . I
am the shepherding WG chair for this document. Please find below the
shepherd write-up for this document:

Shepherd Write-Up:
================

1. Have the chairs personally reviewed this version of the Internet
Draft (ID), and in particular, do they believe this ID is ready to
forward to the IESG for publication?

YES.

   2. Has the document had adequate review from both key WG members
and key  non-WG members? Do you have any concerns about the depth or
breadth of the  reviews that have been performed?

YES, the ID has been adequately reviewed from both key WG members and
key non-WG members.
NO, there is no concern about the reviews.

   3. Do you have concerns that the document needs more review from a
particular  (broader) perspective (e.g., security, operational
complexity, someone familiar with AAA, etc.)?

NO.

   4. Do you have any specific concerns/issues with this document that
you believe
the ADs and/or IESG should be aware of? For example, perhaps you are
uncomfortable with certain parts of the document, or have concerns
whether there really is a need for it. In any event, if your issues
have been discussed in the WG and the WG has indicated it that it
still wishes to advance the document, detail those concerns in the
write-up.

NO.

   5. How solid is the WG consensus behind this document? Does it represent the
strong concurrence of a few individuals, with others being silent, or
does the WG
as a whole understand and agree with it?

GOOD consensus exists behind this document.

   6. Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarize the areas of conflict in separate
email to the Responsible Area Director.

NO. There were no objections raised during the extended WGLC

   7. Have the chairs verified that the document adheres to all of the
ID Checklist items ?

YES.

   8. Is the document split into normative and informative references? Are there
normative references to IDs, where the IDs are not also ready for advancement or
are otherwise in an unclear state? (note here that the RFC editor will
not publish
an RFC with normative references to IDs, it will delay publication
until all such
IDs are also ready for publication as RFCs.)

NO, the document has only informative references and does not split
into normative and informative references.

   9. What is the intended status of the document? (e.g., Proposed
Standard, Informational?)

Informational.

  10.       * Technical Summary

The document discusses Mobile Ad hoc NETworks (MANETs).  It presents
the initial motivation for MANET and describes unaccustomed
characteristics and challenges.  It also defines a MANET, other MANET
entities, and MANET architectural concepts.


          * Working Group Summary

It was required to have the MANET architecture well understood and
documented before focusing on the solution space. Lot of discussion
focused on the addressing and prefix model for MANET, which  was then
integrated and is  reflected in this version of the document.

          * Protocol Quality

This document is the result of a very long discussion and interaction
among the  members of the Internet area in general and MANET group in
particular. The document describes the MANET architecture which has
evolved over the past  several years based on the long MANET protocol
design and implementation experiences.


_______________________________________________
Autoconf mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/autoconf