> From: "Perry E. Metzger" <[EMAIL PROTECTED]>
> Identifier/locator separation has been a topic of conversation at the
> IETF for at least the last decade if not longer. In spite of this
> continuous interest, an actual fruitful proposal has yet to arrive.
As you seem to have forg
> I highly recommend attempting to do a fully worked proposal complete
> with documents before bringing up the topic in a broad audience -- it
> will increase your credibility markedly.
the paradox is that it's difficult to know what requirements
a 'fully worked proposal' must meet without first t
Iljitsch van Beijnum <[EMAIL PROTECTED]> writes:
> As it looks like the long term solution will be some kind of
> identifier/locator separation which will have a huge impact on all
> aspects of IPv6, I think this topic deserves attention from a wider
> audience than it's getting now.
Identifier/l
Date:Mon, 11 Nov 2002 09:57:11 -0500
From:"Alagna, Paul" <[EMAIL PROTECTED]>
Message-ID: <19DE307E1D15D61193690008C75D6E94030BF46A@TBHWMIS5>
| The use of a master list to specify what version is
| current will stop a lot of noise. Suppose edits are to be made to ve
In IPv4, enterprises and other organizations can protect themselves from
ISP and telco outages by connecting to more than one ISP (multihoming).
This means the organization's IP address range must be visible in the
global routing table, which now holds approximately 115,000 routes.
The same thing
At 9:40 +0200 11/9/02, Pekka Savola wrote:
So, it looks like the message sent on lists is trying to reach those
participants who have never been to IETF physical meeting and are
subscribed to a mailing list.
But recall that the IETF's primary form of communication is the
mailing list, not the f
All;
All of this is consistent with documentation management per se. may
I suggest a refinement. The use of a master list to specify what version is
current will stop a lot of noise. Suppose edits are to be made to version 5
to make version 6. the general population can busy themselves with
Dear Keith,
Sorry I couldn't respond earlier (if, that is, a response was expected).
On Thu 2002.11.07, Keith Moore wrote:
> problem is, if you keep the same API, then apps that depend on that API
> will expect that the name space has the same characteristics as DNS,
> (benefits and shortcomin
On 8 Nov 2002, Perry E. Metzger wrote:
> Pekka Savola <[EMAIL PROTECTED]> writes:
> > Seriously, couldn't we cut this crap?
> >
> > At least when I go to the meetings, I can conveniently toss the Note Well
> > statement away, I really don't want to read it N times for every IETF m-l
> > I subscribe
Pekka Savola <[EMAIL PROTECTED]> writes:
> Seriously, couldn't we cut this crap?
>
> At least when I go to the meetings, I can conveniently toss the Note Well
> statement away, I really don't want to read it N times for every IETF m-l
> I subscribe to.
The fact that you're finding yourself annoye
10 matches
Mail list logo
