[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Enum] voipeer agenda/charter uploaded

To: David Meyer <dmm at 1-4-5.net>
Subject: Re: [Enum] voipeer agenda/charter uploaded
From: Christian de Larrinaga <cdel at firsthand.net>
Date: Thu, 13 Oct 2005 12:35:40 +0100
Cc: enum at ietf.org, Stastny Richard <Richard.Stastny at oefeg.at>
In-reply-to: <20051012161220.GA17197@1-4-5.net>
List-help: <mailto:enum-request@ietf.org?subject=help>
List-id: Enum Discussion List <enum.ietf.org>
List-post: <mailto:enum@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
References: <32755D354E6B65498C3BD9FD496C7D461B2190@oefeg-s04.oefeg.loc> <56133BD2-7FD5-4919-B420-DD5A88136AFE@firsthand.net> <20051012161220.GA17197@1-4-5.net>
Sender: enum-bounces at ietf.org

David

It's a framework for clarity in a murky world.

I suspect adding more (than RFC 2826) would only obfuscate rather than enlighten at this point. But I'm willing to listen.

Christian

David

Christian,

I'm not sure why one needs stated support for 2826. Asked

another way, what more (than RFC 2826) needs to be said
about unique roots?

Dave

Christian

_______________________________________________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum

References:
- RE: [Enum] voipeer agenda/charter uploaded
  - From: Stastny Richard
- Re: [Enum] voipeer agenda/charter uploaded
  - From: Christian de Larrinaga
- Re: [Enum] voipeer agenda/charter uploaded
  - From: David Meyer

Prev by Date: Re: [Enum] voipeer agenda/charter uploaded
Next by Date: [Enum] IETF 43 Vancouver Agenda Items
Previous by thread: Re: [Enum] voipeer agenda/charter uploaded
Next by thread: Re: [Enum] voipeer agenda/charter uploaded
Index(es):
- Date
- Thread