Protocol Action: IDPR to Proposed Standard

Internet Engineering Steering Group <iesg-secretary@NRI.Reston.VA.US> Sat, 27 June 1992 02:16 UTC

From: Internet Engineering Steering Group <iesg-secretary@NRI.Reston.VA.US>
To: Bob Braden -- IAB Executive Director <braden@isi.edu>, Internet Activities Board <iab@isi.edu>
Cc: Internet Engineering Task Force <ietf@isi.edu>
Cc: IAB Standard Administrator <IAB-STDS@isi.edu>
Subject: Protocol Action: IDPR to Proposed Standard
Date: Fri, 26 Jun 1992 14:02:22 -0400
Sender: gvaudre@NRI.Reston.VA.US
Message-Id: <9206261402.aa07034@IETF.NRI.Reston.VA.US>

Recommendation:

   The IESG recommends that the InterDomain Policy Routing (IDPR)
   Protocol be elevated to Proposed Standard Status.

   IDPR is define in the Internet Drafts:

   o <draft-ietf-idpr-architecture-04> "An Architecture for Inter-Domain
      Policy Routing" 
   and 

   o <draft-ietf-idpr-specv1-02> "Inter-Domain Policy
      Routing Protocol Specification: Version1"

   An overview document is available as Internet Drafts 
   <draft-ietf-idpr-summary-00> "IDPR as a Proposed Standard".
   IDPR is the product of the IDPR Working Group of the IETF.

Abstract:

   IDPR was developed to fill a perceived need (see RFCs 1092,1102,
   1104, 1124, and 1125) - that of policy-based routing in a large
   internet.  While there are other inter-domain routing procedures
   that are designed for large internets, only IDPR offers the
   potential for full policy routing.  The routes constructed with IDPR
   can account for the transit service providers access restrictions,
   qualities of service, and charging for service.  These routes can
   also account for individual source requirements in terms of service,
   cost, and access restrictions.

Technical Summary:

   IDPR meets the requirements for a Proposed Standard Routing Protocol
   as documented in RFC 1264, "Internet Routing Protocol
   Standardization Criteria".  It is a complete and reasonably
   understood and stable specification that has been validated by
   initial implementation experience.

   IDPR is compatible with the Interdomain/Intradomain routing
   architecture of the Internet.  IDPR can be deployed in an
   incremental manner and without conflict with currently deployed
   routing protocols.  The deployment of IDPR is a step toward support
   of a larger more complex Internet.  This deployment is not in
   conflict with the ongoing efforts to select and develop the next
   generation routing and addressing architecture and associated
   protocols.

Protocol Action: IDPR to Proposed Standard Internet Engineering Steering Group