Hi Adrian,
The attached email arrived from the tool on Friday and TD278/GEN was posted
shortly afterwards:
http://www.itu.int/md/T09-SG15-111205-TD-GEN-0278/en
Regards,
Greg
-----Original Message-----
From: Adrian Farrel [mailto:adrian(_at_)olddog(_dot_)co(_dot_)uk]
Sent: Sunday, 20 November 2011 01:50
To: Jones, Greg
Cc: housley(_at_)vigilsec(_dot_)com; chair(_at_)ietf(_dot_)org;
iesg(_at_)ietf(_dot_)org; Johnson, Malcolm;
yoichi(_dot_)maeda(_at_)ttc(_dot_)or(_dot_)jp; ietf(_at_)ietf(_dot_)org; Eliot
Lear; ietf-secretariat(_at_)ietf(_dot_)org
Subject: New liaison from IESG to SG15
Hi Greg,
Please find below a copy of a Liaison from the IESG to SG15. The liaison is
entered in our tool at https://datatracker.ietf.org/liaison/1115/.
Owing to some glitch in the tool, the liaison does not appear to have popped
out as an email. Because everyone is en route back from IETF-82 in Taipei, this
is going to take a couple of days to emerge, so I am sending you this direct
such that you can get it into the ITU-T system in good time for the December
plenary.
Thanks for your work.
Regards,
Adrian (for the IETF Secretariat)
===
Liaison Statement: Email Correspondence Between IETF Chair and TSB Director
Submission Date: 2011-11-18
From: The IESG (Russ Housley)
To: ITU-T SG 15 (Greg Jones)
Cc:
The IETF Chair
The IESG
Malcolm Johnson
Yoichi Maeda
The IETF
Response Contact: Russ Housley
Technical Contact: Eliot Lear
Purpose: For information
Attachments: (none)
Body:
The IESG would like to draw your attention to an email from the IETF Chair, Mr.
Russ Housley, to the TSB Director, Mr. Malcolm Johnson.
The email is fully supported by the IESG, and reads as follows:
From: Russ Housley <housley(_at_)vigilsec(_dot_)com>
Date: November 15, 2011 5:23:15 AM EST
To: Malcolm Johnson <Malcolm(_dot_)Johnson(_at_)itu(_dot_)int>
Subject: Re: MPLS
Dear Malcolm:
http://www.itu.int/ITU-T/newslog/Statement+Ahead+Of+IETF+Meeting.aspx
Thanks for getting this posted. It has already gotten a lot of visibility.
Just to make sure that we are on the same page, I'd like to repeat two things
that came up while we were drafting the newslog article. These also reflect the
IETF's understanding of the newslog article. I'll forward this note to the
IETF participants to be sure that we're all in sync here.
First, the text of the newslog article re-affirms the JWT agreement from 2008
as captured in RFC 5317. In particular, the IETF standards process will
continue to be used for all MPLS-TP architecture and protocol documents.
Second, since G.8113.1 contains a protocol that is not a product of the IETF
standards process, it cannot be a part of MPLS-TP according to the conditions
of the JWT agreement and the newslog article. The IETF anticipates one of the
following actions will be taken to conform to this agreement. Either (1)
G.8113.1 will be withdrawn, or (2) the title of G.8113.1 will be changed, and
the content will be revised to reflect that it is not included as part of MPLS
or MPLS-TP protocol suite.
Also, thanks for sending me the TD527/P document from the SG15 Chairman. I
note that it proposes the progression of both G.8113.1 and G.8113.2 as MPLS
standards. This approach is not consistent with the JWT agreement or the
newslog article.
I believe this is a constructive step forward. I look forward to a resolution
that fully respects the JWT agreement and moves our two organizations further
toward collaborative standards development.
Russ
--- Begin Message ---
Title: Email Correspondence Between IETF Chair and TSB Director
Submission Date: 2011-11-18
URL of the IETF Web page: /liaison/1115/
From: The IESG (Russ Housley <housley(_at_)vigilsec(_dot_)com>)
To: ITU-T SG 15 (Greg Jones <greg(_dot_)jones(_at_)itu(_dot_)int>)
Cc: The IETF Chair <chair(_at_)ietf(_dot_)org>,The IESG
<iesg(_at_)ietf(_dot_)org>,Malcolm Johnson
<malcolm(_dot_)johnson(_at_)itu(_dot_)int>,Yoichi Maeda
<yoichi(_dot_)maeda(_at_)ttc(_dot_)or(_dot_)jp>,The IETF
<ietf(_at_)ietf(_dot_)org>
Reponse Contact: Russ Housley <chair(_at_)ietf(_dot_)org>
Technical Contact: Eliot Lear <elear(_at_)cisco(_dot_)com>
Purpose: For information
Body: The IESG would like to draw your attention to an email from the IETF
Chair, Mr. Russ Housley, to the TSB Director, Mr. Malcolm Johnson.
The email is fully supported by the IESG, and reads as follows:
From: Russ Housley <housley(_at_)vigilsec(_dot_)com>
Date: November 15, 2011 5:23:15 AM EST
To: Malcolm Johnson <Malcolm(_dot_)Johnson(_at_)itu(_dot_)int>
Subject: Re: MPLS
Dear Malcolm:
http://www.itu.int/ITU-T/newslog/Statement+Ahead+Of+IETF+Meeting.aspx
Thanks for getting this posted. It has already gotten a lot of
visibility.
Just to make sure that we are on the same page, I'd like to repeat two
things that came up while we were drafting the newslog article. These
also reflect the IETF's understanding of the newslog article. I'll
forward this note to the IETF participants to be sure that we're all
in sync here.
First, the text of the newslog article re-affirms the JWT agreement
from 2008 as captured in RFC 5317. In particular, the IETF standards
process will continue to be used for all MPLS-TP architecture and
protocol documents.
Second, since G.8113.1 contains a protocol that is not a product of
the IETF standards process, it cannot be a part of MPLS-TP according
to the conditions of the JWT agreement and the newslog article. The
IETF anticipates one of the following actions will be taken to
conform to this agreement. Either (1) G.8113.1 will be withdrawn, or
(2) the title of G.8113.1 will be changed, and the content will be
revised to reflect that it is not included as part of MPLS or MPLS-TP
protocol suite..
Also, thanks for sending me the TD527/P document from the SG15
Chairman. I note that it proposes the progression of both G.8113.1
and G.8113.2 as MPLS standards. This approach is not consistent with
the JWT agreement or the newslog article.
I believe this is a constructive step forward. I look forward to a
resolution that fully respects the JWT agreement and moves our two
organizations further toward collaborative standards development.
Russ
Attachment(s):
No document has been attached
--- End Message ---
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf