In the Introduction I read "Mind you, the Null Packet is not created by compressing a packet until it disappears into nothingness." That is nice, since I believe that doing so would create a "black hole packet" that would attract and collapse the whole Internet. On the plus side, we would not need to worry anymore about IPv6... On Sun, Apr 1, 2012 at 6:03 PM, <rfc-editor@xxxxxxxxxxxxxx> wrote: > > A new Request for Comments is now available in online RFC libraries. > > > RFC 6592 > > Title: The Null Packet > Author: C. Pignataro > Status: Informational > Stream: Independent > Date: 1 April 2012 > Mailbox: cpignata@xxxxxxxxx > Pages: 6 > Characters: 11036 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-pignataro-the-null-packet-00.txt > > URL: http://www.rfc-editor.org/rfc/rfc6592.txt > > The ever-elusive Null Packet received numerous mentions in documents > in the RFC series, but it has never been explicitly defined. This > memo corrects that omission. This document is not an Internet Standards > Track specification; it is published for informational purposes. > > > INFORMATIONAL: This memo provides information for the Internet community. > It does not specify an Internet standard of any kind. Distribution of > this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@xxxxxxxxxxxxxx. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > >