ftp://ftp.isi.edu/in-notes/rfc2223.txt
RFC2223, "Instructions to RFC Authors" is a great place to start, if you
are considering drafting an RFC to update/change RFC822.
D
At 04:46 PM 6/19/00 -0400, Swerve wrote:
>Hi,
>
>As one of those RSP's and "users" who likes the idea of being able to use
>.@eg.com,
>does anyone know where one can submit suggestions to the body that has
>established RFC822 ?
>
>regards,
>
>Josh Melamed
>shwa@swerve.com
>
> > From: "Derek J. Balling" <dredd@megacity.org>
> > Date: Mon, 19 Jun 2000 13:00:52 -0700
> > To: "William X. Walsh" <william@userfriendly.com>
> > Cc: Mark Collette <mark@hyperbyte.ab.ca>, discuss-list@opensrs.org
> > Subject: Re[4]: "." before the "@"
> >
> > At 12:56 PM 6/19/00 -0700, William X. Walsh wrote:
> >>>> Now the final question, will OpenSRS let the server accept those
> >>>> addresses? I believe that someone already said yes, but I may be
> >>>> wrong.
> >>
> >> DJB> If they do, then the server should be corrected. A domain-registrar
> >> should
> >> DJB> not be playing "fast and loose" with standards. If you want to
> play fast
> >> DJB> and loose, that's your business, but the data that a domain
> registrar is
> >> DJB> presenting to the Internet should ALWAYS abide by that Internet's
> >> DJB> established standards, and that means following RFC822 to the letter.
> >>
> >> When you get all the registrars to do that, this might be a valid
> >> point. Until then, it places us RSPs at a disadvantage.
> >
> > Sorry, I don't see where "obeying the standard" is a disadvantage.
> >
> > You could point out that "The reason you're going with us as a registrar is
> > because - unlike other registrars such as NSI - we actually have a
> > committment to interoperability and standards compliance and not just the
> > almighty dollar. Let's get you set up the 'right way' and not just 'the NSI
> > way'".
> >
> > D
> >
> >
> >
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:38 EDT