Indeed, I second Russ' request. That sort of positive example / success story would help the current interactions around MPLS, and this document a lot.
Gregory.
--
----
IETF related email from
Gregory M. Lebovitz
Juniper Networks
On Thu, Jun 11, 2009 at 7:31 AM, Russ Housley <housley@xxxxxxxxxxxx> wrote:
Dave:
Can you offer a paragraph or so of text to go with the list of documents? Are there any lessons learned or principles that need to be added to the list based on the this experience?
Russ
At 02:59 PM 6/10/2009, Dave CROCKER wrote:
Internet-Drafts@xxxxxxxx wrote:
In particular, this was
achieved via the establishment of the "Joint working team on MPLS-TP"
which was the first ever joint ITU/IETF group.
How quickly we forget:
ITU's T.37 and IETF's:
RFC4142 - Full-mode Fax Profile for Internet Mail (FFPIM)
RFC3950 - Tag Image File Format Fax eXtended (TIFF-FX) -
image/tiff-fx MIME Sub-type Registration
RFC3949 - File Format for Internet Fax
RFC3192 - Minimal FAX address format in Internet Mail
RFC3249 - Implementers Guide for Facsimile Using Internet Mail
RFC3192 - Minimal FAX address format in Internet Mail
RFC2880 - Internet Fax T.30 Feature Mapping
RFC2879 - Content Feature Schema for Internet Fax (V2)
RFC2542 - Terminology and Goals for Internet Fax
RFC2534 - Media Features for Display, Print, and Fax
RFC2532 - Extended Facsimile Using Internet Mail
RFC2531 - Content Feature Schema for Internet Fax
RFC2304 - Minimal FAX address format in Internet Mail
RFC2301 - File Format for Internet Fax
were the result of an 8-year closely cooperative relationship between the two groups.
But it had an extremely rocky start that required careful negotiation to resolve.
d.
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
--
----
IETF related email from
Gregory M. Lebovitz
Juniper Networks
_______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf