[Rmt] FW: [RFC State] <draft-ietf-rmt-bb-fec-raptorq-06> has been added to RFC Editor database
"David Harrington" <ietfdbh@comcast.net> Tue, 21 June 2011 03:28 UTC
Return-Path: <ietfdbh@comcast.net>
X-Original-To: rmt@ietfa.amsl.com
Delivered-To: rmt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id BC80911E80DF for <rmt@ietfa.amsl.com>;
Mon, 20 Jun 2011 20:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level:
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120,
BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AGEAilJtcXLs for
<rmt@ietfa.amsl.com>; Mon, 20 Jun 2011 20:28:37 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net
(qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by ietfa.amsl.com
(Postfix) with ESMTP id 9245811E80DB for <rmt@ietf.org>;
Mon, 20 Jun 2011 20:28:35 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by
qmta03.westchester.pa.mail.comcast.net with comcast id yTF81g0031c6gX853TUc9E;
Tue, 21 Jun 2011 03:28:36 +0000
Received: from davidPC ([67.189.235.106]) by
omta23.westchester.pa.mail.comcast.net with comcast id yTUa1g00m2JQnJT3jTUbtC;
Tue, 21 Jun 2011 03:28:35 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <rmt@ietf.org>
Date: Mon, 20 Jun 2011 23:28:29 -0400
Message-ID: <DBFDAD235BF74C848D44DBA8A643415B@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16807
Thread-Index: Acwvs06GWf9pozxISS+bYvZ0eWCHCQAD+9Hw
Subject: [Rmt] FW: [RFC State] <draft-ietf-rmt-bb-fec-raptorq-06> has been
added to RFC Editor database
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmt>,
<mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmt>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmt>,
<mailto:rmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 03:28:37 -0000
Congratulations. David Harrington Director, IETF Transport Area ietfdbh@comcast.net (preferred for ietf) dbharrington@huaweisymantec.com +1 603 828 1401 (cell) -----Original Message----- From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org] Sent: Monday, June 20, 2011 9:34 PM To: luby@qualcomm.com; amin.shokrollahi@epfl.ch; watsonm@netflix.com; stockhammer@nomor.de; lminder@qualcomm.com Cc: rmt-ads@tools.ietf.org; rmt-chairs@tools.ietf.org; rfc-editor@rfc-editor.org Subject: [RFC State] <draft-ietf-rmt-bb-fec-raptorq-06> has been added to RFC Editor database Author(s), We have received notice that your document draft-ietf-rmt-bb-fec-raptorq-06 has been approved for publication as an RFC. The document has been added to the RFC-Editor queue and you can check the status at <http://www.rfc-editor.org/queue2.html#draft-ietf-rmt-bb-fec-raptorq> ** Note: Please see our News page ** (http://www.rfc-editor.org/news.html) for information regarding the ** transition to the RFC 5378 copyright notice and legends as it ** relates to your document in the RFC Editor queue. If you submitted your XML file using the I-D submission tool, we have already retrieved it. If you did not submit the XML file via the I-D submission tool, or if you have an updated version (e.g., updated contact information), please send us the XML file at this time. Please attach the file as draft-ietf-rmt-bb-fec-raptorq-06.xml, and specify any differences between the approved I-D and the document that the XML produces. If you created this document using -ms nroff, please send us the source file. This should help increase the pace with which documents move through the RFC-Editor queue. Please let us know if you have any questions. Thank you. The RFC-Editor Team
- [Rmt] FW: [RFC State] <draft-ietf-rmt-bb-fec-rapt… David Harrington