RFC 796 (Address Mappings) to Historic
status-change-ipv4-address-mapping-classes-to-historic-01
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2014-04-28
|
01 | Cindy Morgan | The following approval message was sent From: The IESG To: IETF-Announce Cc: RFC Editor , gds@gds.best.vwh.net, sunset4-chairs@tools.ietf.org Subject: Document Action: Address mappings to Historic … The following approval message was sent From: The IESG To: IETF-Announce Cc: RFC Editor , gds@gds.best.vwh.net, sunset4-chairs@tools.ietf.org Subject: Document Action: Address mappings to Historic The IESG has approved changing the status of the following document: - Address mappings (rfc796) to Historic This document action is documented at: http://datatracker.ietf.org/doc/status-change-ipv4-address-mapping-classes-to-historic/ A URL of the affected document is: http://datatracker.ietf.org/doc/rfc796/ Status Change Details: RFC 796 [RFC796] specifies formats for "classful" IPv4 addresses. It also specifies mappings for some existing networks at the time it was published between their "local" network representations and IPv4 equivalents. However, "classful" addresses have been largely superseded by CIDR [RFC4632]. Furthermore, the vast majority of these addresses have either been reassigned to other organizations, or are considered part of private address space [RFC1918]. Therefore, RFC 796 is reclassified to Historic status. Personnel Ted Lemon is the responsible Area Director. |
2014-04-28
|
01 | Cindy Morgan | IESG has approved the status change |
2014-04-28
|
01 | Cindy Morgan | Closed "Approve" ballot |
2014-04-28
|
01 | Cindy Morgan | RFC Status Change state changed to Approved - announcement sent from Approved - announcement to be sent |
2014-04-24
|
01 | Cindy Morgan | RFC Status Change state changed to Approved - announcement to be sent from IESG Evaluation |
2014-04-24
|
01 | Stephen Farrell | [Ballot Position Update] New position, No Objection, has been recorded for Stephen Farrell |
2014-04-24
|
01 | Kathleen Moriarty | [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty |
2014-04-24
|
01 | Benoît Claise | [Ballot Position Update] New position, No Objection, has been recorded for Benoit Claise |
2014-04-23
|
01 | Pete Resnick | [Ballot Position Update] New position, No Objection, has been recorded for Pete Resnick |
2014-04-23
|
01 | Richard Barnes | [Ballot Position Update] New position, No Objection, has been recorded for Richard Barnes |
2014-04-23
|
01 | Martin Stiemerling | [Ballot Position Update] New position, No Objection, has been recorded for Martin Stiemerling |
2014-04-22
|
01 | Brian Haberman | [Ballot Position Update] New position, No Objection, has been recorded for Brian Haberman |
2014-04-20
|
01 | Joel Jaeggli | [Ballot Position Update] New position, No Objection, has been recorded for Joel Jaeggli |
2014-04-18
|
01 | Alissa Cooper | [Ballot Position Update] New position, No Objection, has been recorded for Alissa Cooper |
2014-04-16
|
01 | Adrian Farrel | [Ballot comment] Greg Skinner supplied me with the information I needed. I leave it up to the responsible AD to decide whether he wants to … [Ballot comment] Greg Skinner supplied me with the information I needed. I leave it up to the responsible AD to decide whether he wants to update the Status Change Note. |
2014-04-16
|
01 | Adrian Farrel | [Ballot Position Update] Position for Adrian Farrel has been changed to No Objection from Discuss |
2014-04-16
|
01 | Adrian Farrel | [Ballot discuss] I find myself wanting to have a brief Discussion about the text in the Status Change document. I rather regret that because this … [Ballot discuss] I find myself wanting to have a brief Discussion about the text in the Status Change document. I rather regret that because this "move to Historic" has already taken up more time than it was worth spending on it. > RFC 796 [RFC796] specifies formats for "classful" IPv4 addresses. > It also specifies mappings for some existing networks at the time it > was published between their "local" network representations and > IPv4 equivalents. However, "classful" addresses have been largely > superseded by CIDR [RFC4632]. Furthermore, the vast majority of > these addresses have either been reassigned to other organizations, > or are considered part of private address space [RFC1918]. > Therefore, RFC 796 is reclassified to Historic status. "Largely superseded" means that some are still in use. "vast majority..." means that some are still in use. What is the status of those classful addresses when this RFC is marked as Historic? Where does one go to read a current description of their usage and for mappings of the networks that are still in use? |
2014-04-16
|
01 | Adrian Farrel | [Ballot Position Update] New position, Discuss, has been recorded for Adrian Farrel |
2014-04-15
|
01 | Spencer Dawkins | [Ballot Position Update] New position, No Objection, has been recorded for Spencer Dawkins |
2014-04-15
|
01 | Barry Leiba | [Ballot Position Update] New position, No Objection, has been recorded for Barry Leiba |
2014-04-15
|
01 | Ted Lemon | Placed on agenda for telechat - 2014-04-24 |
2014-04-15
|
01 | Ted Lemon | [Ballot Position Update] New position, Yes, has been recorded for Ted Lemon |
2014-04-15
|
01 | Ted Lemon | Created "Approve" ballot |
2014-04-15
|
01 | Ted Lemon | RFC Status Change state changed to IESG Evaluation from Waiting for AD Go-Ahead |
2014-04-15
|
01 | Ted Lemon | We got exactly one response to this, from Ralph Droms, who was in favor. |
2014-03-27
|
01 | (System) | RFC Status Change state changed to Waiting for AD Go-Ahead from In Last Call |
2014-02-27
|
01 | Cindy Morgan | The following Last Call announcement was sent out: From: The IESG To: IETF-Announce Reply-To: ietf@ietf.org Sender: Subject: Last Call: RFC 796 (Address Mappings) to Historic … The following Last Call announcement was sent out: From: The IESG To: IETF-Announce Reply-To: ietf@ietf.org Sender: Subject: Last Call: RFC 796 (Address Mappings) to Historic The IESG has received a request from an individual participant to make the following status changes: - RFC796 from Unknown to Historic (Address mappings) The supporting document for this request can be found here: http://datatracker.ietf.org/doc/status-change-ipv4-address-mapping-classes-to-historic/ The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2014-03-27. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The affected document can be obtained via http://datatracker.ietf.org/doc/rfc796/ IESG discussion of this request can be tracked via http://datatracker.ietf.org/doc/status-change-ipv4-address-mapping-classes-to-historic/ballot/ |
2014-02-27
|
01 | Cindy Morgan | RFC Status Change state changed to In Last Call from Last Call Requested |
2014-02-27
|
01 | Cindy Morgan | Last call announcement was generated |
2014-02-27
|
01 | Ted Lemon | Last call was requested |
2014-02-27
|
01 | Ted Lemon | Ballot approval text was generated |
2014-02-27
|
01 | Ted Lemon | Ballot writeup was generated |
2014-02-27
|
01 | Ted Lemon | RFC Status Change state changed to Last Call Requested from AD Review |
2014-02-27
|
01 | Ted Lemon | New version available: status-change-ipv4-address-mapping-classes-to-historic-01.txt |
2014-02-27
|
00 | Ted Lemon | New version available: status-change-ipv4-address-mapping-classes-to-historic-00.txt |
2014-02-25
|
00 | Ted Lemon | Last call announcement was generated |