> A deprecated address is still a valid address, and can be used for > anything at all. > > However, they're addresses that the intent is to stop using sometime > soon, and if we don't want to break connections when the address becomes > invalid, we should try to avoid using them when possible. > > But that doesn't mean that we break/refuse existing communications > earlier than we need to to achieve that. > > If I have an address, A1, which is goingto change to A2, what I do is > make A1 deprecated, and A2 preferred, and at (more or less) the same > time I start announcing via the DNS the A2 address instead of the A1 > address. > > Remote nodes will take something between hours, and days, depending > on DNS TTLs to detect the change from A1 to A2 - in the interim period the > only address they have is A1, that's the only one they can use.
entirely agree. and it's also not reasonable to assume that every application component that has knowledge of an old address is periodically checking DNS - the app might not even be getting its addresses from DNS, and there might not be a reliable DNS name that is bound to the node the app wants to talk to. deprecated addresses should stop working only when the network stops forwarding those packets to hosts - there's no need for hosts to break them prematurely. Keith -------------------------------------------------------------------- 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] --------------------------------------------------------------------
