![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
----- Original Message ----- From: "Randall Gellens" <randy at qualcomm.com> To: "John C Klensin" <john-ietf at jck.com>; "Harald Alvestrand" <harald at alvestrand.no> Cc: <ietf at ietf.org>; <ima at ietf.org> Sent: Thursday, January 18, 2007 6:44 AM Subject: Re: [EAI] Last Call: draft-ietf-eai-framework (Overview and Framework for Internationalized Email) to Informational RFC > At 4:02 PM -0500 1/17/07, John C Klensin wrote: > >> In any event, I'd recommend/request that you specify >> text and where it should go. > > I'm thinking a brief mention in the Framework document, with more > discussion in the SMTP extension document, and maybe a mention in the > downgrade document. I'll suggest text for those documents later, but > for the Frameworks document, immediately following the two bullets in > Section 4.3, add a new paragraph: If no one else objects it, I will update it in SMTPext document according to your suggestions. Thanks. YAO Jiankang CNNIC > > ----------------------- > (The client can also try an alternate next-hop host or requeue the > message and try later, on the assumption that the lack of UTF8SMTP is > a transient failure; since this ultimately resolves to success or > failure, it doesn't change the discussion here.) > ----------------------- > > > -- > Randall Gellens > Opinions are personal; facts are suspect; I speak for myself only > -------------- Randomly-selected tag: --------------- > Seduced, shaggy Samson snored. > She scissored short. Sorely shorn, > Soon shackled slave, Samson sighed, > Silently scheming, > Sightlessly seeking > Some savage, spectacular suicide. > --Stanislaw Lem > > _______________________________________________ > Ietf mailing list > Ietf at ietf.org > https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.