"Alan E. Beard" <[EMAIL PROTECTED]> wrote:

[...]
|Additionally, such a suggestion, if implemented, would effectively
|prohibit one of the chief *legitimate* uses of GUPI address address
|allocations: routing between private networks on private (or VPN) links
|under bilateral agreements between the end networks.
[...]
|* Manufacturers of routers MUST include in router code a routing black
|hole for the entire unique-local address block. Router manufacturers MUST
|ensure that said black hole cannot be deconfigured, turned off, or
|otherwise overridden in toto;

Please don't do this.  I don't want to have to special-case all my interior
routers (that could otherwise get by with simple default routes for much of
the outside world--including tunnels to other GUPI address space) for each
tunnel that might be available at the edge routers.  This will be even more
of a problem once we start to set up dynamic tunnels so that a large set of
GUPI-using-sites can communicate in a cooperative overlay network.  There is
no way to know whether a router will be used at the edge where you *might*
have some business enforcing such a black hole or deep inside where you have
absolutely no business complicating my routing.

|however, manufacturers MAY provide a
|configuration facility to "punch through" the black hole for
|user-specified prefixes within the unique-local block.

But I will probably want to send the *whole* unique-local block to a tunnel
router of some sort.

|Router
|manufacturers SHOULD include in user documentation language to the effect
|that routing of unique-local prefixes beyond site boundaries contravenes
|IETF recommendations,

Above you said that routing between private networks was legitimate.  This
certainly involves routing beyond site boundaries.  We need to make it clear
that "beyond site boundaries" does not equate to "on the public internet".

                                Dan Lanciani
                                [EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to