As one of the authors of the text being discussed, I can confirm that
the intent for the "SHOULD NOT use deprecated address as source" was
for "active opens" only, not on (say) passive opens.
[EMAIL PROTECTED] writes:
> RFC2462
> page 3:
> > in arbitrary communication is unrestricted. Later, an address becomes
> > "deprecated" in anticipation that its current interface binding will
> > become invalid. While in a deprecated state, the use of an address is
> > discouraged, but not strictly forbidden. New communication (e.g.,
> > the opening of a new TCP connection) should use a preferred address
> > when possible. A deprecated address should be used only by
> > applications that have been using it and would have difficulty
> > switching to another address without a service disruption.
> the last sentence does not meet people's understand. append
> ", or there is no other choice than to use deprecated address".
> or, since this is introduction section, we shouldn't go into this
> detail here.
The introduction shouldn't/needn't be the definitive text. But if we
can make it more clear, we should.
How about changing:
(e.g.,the opening of a new TCP connection)
to
(e.g., an active open of a new TCP connection)
I'm assuming that "active open" vs. "passive open" terminology is
well-understood (I think it's in RFC 1122).
Thomas
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
