Reject Route case is a specific case of the more general 
"administrative prohibition".

The administrative prohibition case might include other reasons
like "source not allowed", "destination not allowed", "protocol 
not allowed", "port not allowed", "in-secure packets not allowed",
etc.

Second paragraph of section 6.0 in draft 
draft-ietf-ipv6-unique-local-addr-02.txt talks about a black hole 
route for Local IPv6 prefix FC00::/7 and an appropriate ICMPv6
destination unreachable message. The new code "reject route to
destination" is supposed to fulfill that need.

I changed the name to "reject route" from "black hole route"
because a "black hole route", as per the name, should drop the 
packet silently without notifying the sender.

Regards
Mukesh

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 29, 2004 5:55 PM
> To: Gupta Mukesh (Nokia-NET/MtView)
> Cc: [EMAIL PROTECTED]
> Subject: Re: ICMPv6: New destination unreachable codes 
> 
> 
>    If the reason for the failure to deliver is administrative
>    prohibition, e.g., a "firewall filter", the Code field is set to 1.
> 
>    If the reason for the failure to deliver is that packets with this
>    source address is not allowed due to ingress filtering 
> policies, the
>    Code field is set to 5.
> 
>    If the reason for the failure to deliver is that the route to the
>    destination is a reject route, the Code field is set to 6. 
>  This may
>    occur if the router has been configured to reject all the 
> traffic for
>    a specific prefix.
> 
> Isn't a reject route just a simple type of firewall/administrative
> prohibition?  Likewise for ingress filtering?  
> 
> Is the intent to distinguish between "packet was dropped because
> policy says packets from that source should be dropped" and "packet
> was dropped because policy says that packets to that destination
> should be dropped"?  
> 
>                                               - Bill
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to