[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Distributing site-wide RFC 3484 policy
- To: IPv6 Operations <v6ops@ops.ietf.org>
- Subject: Distributing site-wide RFC 3484 policy
- From: Brian E Carpenter <brian.e.carpenter@gmail.com>
- Date: Mon, 23 Jul 2007 20:56:29 +0200
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=GYFG0T0PwjQS2Mr+UmpLK1C3W3ydZXR/eFJyvO+StO3onWBmulPLCbVq6lVxgg0eJhmgsGeBbzQ/PMrZJbHU+8bthgAhsF36QrXlZ336mz3XsANq/RFeRnuj8ZrGuU3TMsubxEuBLsnVHbbCFi8ibP8qr7nSpcAafRG/JHkbBBY=
- User-agent: Thunderbird 1.5.0.12 (Windows/20070509)
What happened to
http://tools.ietf.org/id/draft-hirotaka-dhc-source-address-selection-opt-01.txt
and is there any other proposal for site-wide distribution of
address selection policy?
As I said at the mike today, I really think we can't avoid
such a mechanism. There *will* be sites running multiple prefixes
(those too small to insist on PI space, but big enough to
need multiple ISPs).
Brian