Re: Experimental RFC to be: <draft-irtf-dtnrg-bundle-previous-hop-block-12.txt>

The IESG <iesg-secretary@ietf.org> Tue, 22 February 2011 22:38 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9F543A6983; Tue, 22 Feb 2011 14:38:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.142
X-Spam-Level:
X-Spam-Status: No, score=-102.142 tagged_above=-999 required=5 tests=[AWL=-0.342, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rEjaupq+2flh; Tue, 22 Feb 2011 14:38:05 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6919F3A6987; Tue, 22 Feb 2011 14:38:05 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: irsg@isi.edu
Subject: Re: Experimental RFC to be: <draft-irtf-dtnrg-bundle-previous-hop-block-12.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110222223805.7731.69502.idtracker@localhost>
Date: Tue, 22 Feb 2011 14:38:05 -0800
Cc: iana@iana.org, elwynd@dial.pipex.com, The IESG <iesg@ietf.org>, ietf-announce@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 22:38:06 -0000

The IESG has no problem with the publication of 'Delay-Tolerant
Networking Previous Hop Insertion Block'
<draft-irtf-dtnrg-bundle-previous-hop-block-12.txt> as an Experimental
RFC.

The IESG would also like the IRSG to review the comments in
the datatracker
(http://datatracker.ietf.org/doc/draft-irtf-dtnrg-bundle-previous-hop-block/)
related to this document and determine whether or not they merit
incorporation into the document. Comments may exist in both the ballot
and the comment log.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-irtf-dtnrg-bundle-previous-hop-block/

The process for such documents is described at
http://www.rfc-editor.org/indsubs.html

Thank you,

The IESG Secretary




Technical Summary

   This document defines an extension block for use with the DTN Bundle
   Protocol.  This Previous Hop Insertion Block (PHIB) extension block
   is designed to be inserted by a forwarding node to provide the
   endpoint identifier (EID) of an endpoint of which the forwarding node
   is a member so that this EID may be conveyed to the next-hop
   receiving node.  Knowledge of an EID of an endpoint of which a
   previous-hop node is a member may be required in some circumstances
   to support certain routing protocols (e.g., flood routing).  If this
   EID cannot be provided by the convergence layer or other means, the
   PHIB defines the mechanism whereby the EID can be provided with the
   bundle.  Each PHIB is always removed from the bundle by the receiving
   node so that its presence within the bundle is limited to exactly one
   hop.  This document defines the format and processing of this PHIB.

Working Group Summary

   This document is a product of the Delay Tolerant Networking Research
   Group and has been reviewed by that group.  No objections to its
   publication as an RFC were raised.

Document Quality

   This is a research document.

Personnel

   The responsible area director is Sean Turner.
   The DTNRG chairs are Kevin Fall and Stephen Farrell.

RFC Editor Note

    Per RFC 5742 our recommendation is the following:

   1. The IESG has concluded that there is no conflict between this 
      document and IETF work.