Tony Hansen | 14 Dec 2003 02:17
Picon
Favicon

Re: draft-ietf-ngtrans-ipv6-smtp-requirement-07.txt


I agree completely -- get it out there as its own RFC. Anything appropriate for 
2821bis can be added whenever that draft starts circulating.

	Tony Hansen
	tony <at> att.com

Keith Moore wrote:
> Personal opinion: I believe the document will have more impact if 
> published separately from the revision to RFC 2821.  I also believe that 
> tying this to the revision of RFC 2821 would significantly delay a 
> published specification for how to use SMTP in the IPv6 world.
> 
> On Dec 10, 2003, at 10:47 PM, Jun-ichiro itojun Hagino wrote:
>>>     an updated version of draft-ietf-ngtrans-ipv6-smtp-requirement
>>>     is attached.
>>>
>>>     to ADs: it may not reflect all the coments i have received, but 
>>> anyways
>>>     better than nothing.  i think it should really be integrated into
>>>     update to RFC2821 (instead of being standalone document).
>>>     it is still using "ngtrans" in the name, however, it is suggested 
>>> that
>>>     the document should be discussed in APP area (there's no 
>>> email-related
>>>     WG exist at this point).
>>
>>     ADs: let me know how to proceed on this document.  should we propose
>>     changes to RFC2821, or?  tnx.

(Continue reading)

Jun-ichiro itojun Hagino | 15 Dec 2003 01:15

Re: draft-ietf-ngtrans-ipv6-smtp-requirement-07.txt


> > Personal opinion: I believe the document will have more impact if 
> > published separately from the revision to RFC 2821.  I also believe that 
> > tying this to the revision of RFC 2821 would significantly delay a 
> > published specification for how to use SMTP in the IPv6 world.
> I agree completely -- get it out there as its own RFC. Anything appropriate for 
> 2821bis can be added whenever that draft starts circulating.

	ok, i see the point.  then question to the ADs - is the current draft
	sufficient, or it sill need fixing?  (i know it's holiday season
	over there already so no need to hurry)

itojun


Gmane