IAB Protocol Action: IDPR to Proposed Standard
Bob Braden <braden@isi.edu> Sun, 23 August 1992 03:48 UTC
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa03412; 22 Aug 92 23:48 EDT
Received: from venera.isi.edu by NRI.Reston.VA.US id aa15553; 22 Aug 92 23:50 EDT
Received: by venera.isi.edu (5.65c/5.65+local-6) id <AA08081>; Sat, 22 Aug 1992 14:25:57 -0700
From: Bob Braden <braden@isi.edu>
Received: from braden.isi.edu by venera.isi.edu (5.65c/5.65+local-6) id <AA08077>; Sat, 22 Aug 1992 14:25:53 -0700
Date: Sat, 22 Aug 1992 14:25:25 -0700
Posted-Date: Sat, 22 Aug 1992 14:25:25 -0700
Message-Id: <199208222125.AA15996@braden.isi.edu>
Received: by braden.isi.edu (5.65c/4.0.3-4) id <AA15996>; Sat, 22 Aug 1992 14:25:25 -0700
To: ietf@isi.edu
Subject: IAB Protocol Action: IDPR to Proposed Standard
Cc: iab@isi.edu, iab-stds@isi.edu, iesg@isi.edu
Status: O
The IAB has accepted the IESG recommendation 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. Rationale: In May 1989, Dave Clark published RFC-1102, "Policy Routing in Internet Protocols". After three years of further development within IETF, many of these ideas have been realized in IDPR. Unfortunately, it is not clear that there is even "rough consensus" on all particulars of this IDPR specification. This divergence of expert opinion was reflected in the lengthy technical debate following the Last Call and in many private comments. However, we believe that the general policy routing provided by IDPR (following Clark's model) may be important to the future of the Internet, and that talking about it is not enough; experience is needed. The Working Group has stated, and the IESG has agreed, that designating IDPR a Proposed Standard will foster a process of prototyping and limited deployment, to allow the Internet technical community can gather some needed experience with policy routing. To quote from the IESG summary: "IDPR can be deployed in an incremental manner and without conflict with currently deployed routing protocols. ... This deployment is not in conflict with the ongoing efforts to select and develop the next generation routing and addressing architecture and associated protocols." IDPR has satisfied all formal requirements (ref. RFC-1264) for entering a new routing protocol into the standards track, so there are no procedural grounds for deferring its entry. Standardizing a technical specification is not meant to imply anything about its applicability, i.e., when and if it is appropriate to use IDPR. For guidance on the applicability of IDPR, refer to the forthcoming Router Requirements specification.