Virtual Enterprise Traversal (VET)
RFC 5558

State Change Notice email list have been change to steven.w.russert@boeing.com, seung.yi@boeing.com, fltemplin@acm.org, draft-templin-autoconf-dhcp@tools.ietf.org, rfc-editor@rfc-editor.org from steven.w.russert@boeing.com, seung.yi@boeing.com, fltemplin@acm.org, draft-templin-autoconf-dhcp@tools.ietf.org

[Ballot discuss]
This is a discuss discuss; I will clear on the call unless this prompts some change in
consensus amongst the IESG...

I was a bit concerned by section 5 - post-configuration operation.  This seems out of scope,
and I am concerned that the content could unnecessarily constrain future wg activities.  This
is not based on any actual facts, just a vague unesay feeling, which is why I want to hear some
other opinions.

IANA Evaluation comments:

Upon approval of this document, the IANA will make the following assignment
in the "Internet Multicast Addresses" registry located at
http://www.iana.org/assignments/multicast-addresses
sub-registry "224.0.0/24" Local Network Control Block"

224.0.0.TBD "DHCPv4 server discovery" [RFC-templin-autoconf-dhcp-16.txt]


We understand the above to be the only IANA Action for this document.

This RFC-to-be was submitted to the RFC Editor to be published as
Informational: draft-templin-autoconf-dhcp-16.txt

Please let us know if this document conflicts with the IETF standards
process or other work being done in the IETF community.

Four week timeout expires on 23 September 2008.

MANET Autoconfiguration using Virtual Enterprise Traversal (VET)

Mobile Ad-hoc Networks (MANETs) connect routers on links with
asymmetric reachability characteristics, and may also connect to
other networks including the Internet. Routers in MANETs must have
a way to automatically provision IP addresses/prefixes and other
information. This document specifies a Virtual Enterprise
Traversal (VET) abstraction for autoconfiguration and operation of
routers in MANETs.