> > > |- If there is no match (I have only PUPI and DNS returns PA, or vice > > > |versa), I would suggest to fail the connection by default (even though > it > > > |might work), but I am not sure. > > > > > > As long as this default can be changed without the cooperation on the > > > applications (i.e., a global option for the stack) it would be ok... > > > > Modifications to the address selection policy table would help in > achieving > > this default without any change to the applications. > > unless you get conflicting policy from different interfaces, which is > entirely > possible.
I am saying that a modification to the policy table (which is per host, and not per interface) is a solution. You can do it manually or through an automated mechanism. If you are using an automated mechanism, as I had suggested, getting conflicting policy from different interfaces implies that something wrong with the network engineering. There should be a way to detect it. > per-link policy is the wrong way to think about this. what you want is for > each network to be able to say "here's the best way to get here from there > given a variety of conditions"... and then minimize the number of conditions. I am not able to understand the text. Can you provide an example? CP -------------------------------------------------------------------- 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] --------------------------------------------------------------------
