RE: [Mip4] Additional 3344bis error codes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Mip4] Additional 3344bis error codes



Henrik,

How about the following error codes:

- MN-HA Auth failure
- MN-AAA Auth failure
- MN-AAA Authentication timed out with AAA

(Note: currently "MN Auth failure" is sent as a generic error code for
all the above)

- Dynamic Home address is not available (IP Pool exhausted)
- Static home address not available 
- Require reverse-tunnel for private home address
- Improper ordering of extensions (Note: currently "poorly formed
request" is overloaded for this)

-Kuntal


> -----Original Message-----
> From: mip4-bounces at ietf.org [mailto:mip4-bounces at ietf.org] On Behalf
Of
> Henrik Levkowetz
> Sent: Thursday, November 17, 2005 2:54 PM
> To: Charles E. Perkins; Mobile IPv4 Mailing List; Pete McCann
> Subject: [Mip4] Additional 3344bis error codes
> 
> Hi,
> 
>     I've had some feedback from the people at ipUnplugged, who have
> run into some new error cases in deployments of MIPv4 where dynamic
> home address allocation has been used.  After some iterations and
> experience with code discovering and reporting on the error cases,
> it seems the following 4 HA error codes would be appropriate:
> 
> 
> 	* home address already in use (as care-of address)
> 	* care-of address already in use (as home address)
> 	* home address is not unicast
> 	* care-of address is not unicast
> 
> Could we consider adding these to the "Registration denied by the
> home agent" error codes in Section 3.4?
> 
> 
> ( Oh, and incidentally - 3344bis refers to RFC 1700, as reference
[21],
> but RFC 1700 has been replaced by IANA's online database, according to
> RFC 3232, so reference [21] should probably point to the IANA web-site
> and specifically to http://www.iana.org/assignments/mobileip-numbers
.)
> 
> 
> 	Henrik


"This email message and any attachments are confidential information of Starent Networks, Corp. The information transmitted may not be used to create or change any contractual obligations of Starent Networks, Corp.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this e-mail and its attachments by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify the sender immediately -- by replying to this message or by sending an email to postmaster at starentnetworks.com -- and destroy all copies of this message and any attachments without reading or disclosing their contents. Thank you."

--
Mip4 mailing list: Mip4 at ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.