Cisco's Mobile IPv4 Host Configuration Extensions
draft-leung-cisco-mip4-host-config-04

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: RFC Editor <rfc-editor@rfc-editor.org>
Cc: The IESG <iesg@ietf.org>, <iana@iana.org>, ietf-announce@ietf.org
Subject: Re: Informational RFC to be: 
         draft-leung-cisco-mip4-host-config-05.txt 

The IESG has no problem with the publication of 'Cisco's Mobile IPv4 Host 
Configuration Extensions' <draft-leung-cisco-mip4-host-config-05.txt> as 
an Informational RFC. 

The IESG would also like the IRSG or RFC-Editor to review the comments in 
the datatracker 
(https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13046&rfc_flag=0) 
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is Margaret Wasserman.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-leung-cisco-mip4-host-config-05.txt


The process for such documents is described at http://www.rfc-editor.org/indsubs.html.

Thank you,

The IESG Secretary

Ballot Text

This is an RFC Editor submission, and it does not conflice with an ongoing IETF
work, so it is proposed to return the following response:

   1. The IESG has not found any conflict between this document and IETF
      work.

IESG Note

RFC Editor, please include the following standard IESG note:

      This RFC is not a candidate for any level of Internet Standard.
      The IETF disclaims any knowledge of the fitness of this RFC for
      any purpose and in particular notes that the decision to publish
      is not based on IETF review for such things as security,
      congestion control, or inappropriate interaction with deployed
      protocols.  The RFC Editor has chosen to publish this document at
      its discretion.  Readers of this document should exercise caution
      in evaluating its value for implementation and deployment.  See
      RFC 3932 for more information. 

      This RFC does not offer any security mechanisms to provide 
      data origin authentication and integrity, yet these
      security services are vitally important in this context.

RFC Editor Note