[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Enum] Message from Working Group Chair
Thanks Dave for pointing this out.
Due to bad food on the flight back from the IETF in London, I have been
completely offline the last week, and will slowly recover the coming 2-3
weeks.
As Dave points out, this mailing list is for the ENUM working group in the
IETF. I have seen on messages that the mailman stuff at ietf.org seems to
not be working, and I will talk with the administrator about this.
The charter of the wg is defined as seen on the IETF website, and anything
outside what is specified on that charter is out of scope, and not suitable
for discussion on this mailing list.
Regarding competition, I urge people which argue for competition using a
naming mechanism which is not based on the unique naming in DNS (i.e. more
than one root in the DNS tree is used) and this draft MUST contain issues
like:
- Specific algorithms used for party which want to store things in
DNS (the party which want to be called)
- Specific algorithms used for party which want to lookup things
in DNS (the party which makes the call)
Notice that I explicitly say that DNS is used, DNS which does not have
searches. And, given that DNS is used, RFC 2826 MUST be referenced and all
questions and concernes in RFC 2826 MUST be clearly addressed.
When you have published that I-D as an individual submission, let the
working group chairs know, and we will make a decision whether the document
is to be part of the working group charter.
Having arguments and discussions without documents turn the discussions
into pie throwing exercises.
Until such document exists, I will as wg chair decide that RFC 2916 is what
this WG is referencing, and RFC 2916 talks about one root in the DNS
hierarchy. Because of this, this mailing list is NOT for discussion on
"alternate roots" before documents exists which explain in great detail how
that is to work technically given requirements in RFC 2826.
I also urge people which DO belive in RFC 2916 to also write documents
which talk about how "competition" is handled (choice for the holder of the
E.164 number to get good service etc), and proceed like I describe above.
Regards, Patrik
--On 08/17/2001 3:34 PM -0700 Dave Crocker <dhc@dcrocker.net> wrote:
>
>
> Folks,
>
> This is an IETF mailing list. It is for technical discussions for the
> purpose of specifying standards.
>
> This thread is entirely irrelevant to such an activity.
>
> Please move it elsewhere.
>
> d/
>
> ps. And for those who understand and respect this matter of appropriate
> scope and venue, it is important not to respond to further messages in
> this thread.
>
> ----------
> Dave Crocker <mailto:dcrocker@brandenburg.com>
> Brandenburg InternetWorking <http://www.brandenburg.com>
> tel +1.408.246.8253; fax +1.408.273.6464
>
>
> _______________________________________________
> enum mailing list
> enum@ietf.org
> http://www1.ietf.org/mailman/listinfo/enum
>
Patrik Fältström <paf@cisco.com> Cisco Systems
Consulting Engineer Office of the CSO
Phone: (Stockholm) +46-8-6859131 (San Jose) +1-408-525-8509
PGP: 2DFC AAF6 16F0 F276 7843 2DC1 BC79 51D9 7D25 B8DC
_______________________________________________
enum mailing list
enum@ietf.org
http://www1.ietf.org/mailman/listinfo/enum