Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic

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

To: iesg@xxxxxxxx, ietf@xxxxxxxx
Subject: Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic
From: S Moonesamy <sm+ietf@xxxxxxxxxxxx>
Date: Tue, 19 Jun 2018 15:23:20 -0700
In-reply-to: <152588285893.3989.7909763661642193132.idtracker@ietfa.amsl .com>
References: <152588285893.3989.7909763661642193132.idtracker@ietfa.amsl.com>

Dear Internet Engineering Steering Group,

There is an item on the agenda above moving RFC 4405, RFC 4406 andRFC 4407 to Historic. RFC 4405 defines the SUBMITTER ServiceExtension. Is there any standards action needed for the SMTP ServiceExtensions registry?


Regards,
S. Moonesamy

Follow-Ups:
- Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic
  - From: Alexey Melnikov

Prev by Date: Nomcom volunteer list consideration regarding the new Limited Liability Corporation (LLC)
Next by Date: Genart telechat review of draft-ietf-ippm-twamp-yang-11
Previous by thread: Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic
Next by thread: Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic
Index(es):
- Date
- Thread

[Index of Archives] [IETF Annoucements] [IETF] [IP Storage] [Yosemite News] [Linux SCTP] [Linux Newbies] [Mhonarc] [Fedora Users]

Powered by Linux