Return-Path: <stbryant@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
 with ESMTP id 43D6E21F91B7; Tue,  9 Apr 2013 02:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No,
 score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dI2x4XcPa019;
 Tue,  9 Apr 2013 02:34:29 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147])
 by ietfa.amsl.com (Postfix) with ESMTP id 6923621F913C;
 Tue,  9 Apr 2013 02:34:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com;
 l=10177; q=dns/txt; s=iport; t=1365500068; x=1366709668;
 h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to;
 bh=8aMBvqdgZ2tknEB9/WnaoEdaUkvDh1PW7ZAszJ37AO4=;
 b=DHfHisrERuDTPUpuF0R3/gkSBuwgV9hJCwHtYHkAuW4mj2Oaj3e1Et7y
 8R3mMRsvM6vfYpvPfz14VLh5dC7XiBoQPmvLOIteznGQMxzupPQvaUS0Z
 ztjA78NkdZ/eNYWtqZbzEXLWY1mVsVxcLCbvKs+5QfdZd2ditMcRgqiOi c=; 
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAHzfY1GQ/khM/2dsb2JhbABOA4JCRDaJCbg3gRIWdIIfAQEBBAEBASpBCgEQCxEEAQEBCRYIBwkDAgECARUfCQgGDQEFAgEBiBAMrgOQPYkKhggFCwYBEYMwA5Z0gSGPbIMM
X-IronPort-AV: E=Sophos; i="4.87,437,1363132800"; d="scan'208,217";
 a="13203158"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com
 with ESMTP; 09 Apr 2013 09:34:27 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by
 ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r399YPk4005455
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Tue, 9 Apr 2013 09:34:25 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com
 (8.14.4+Sun/8.8.8) with ESMTP id r399YNSC010508;
 Tue, 9 Apr 2013 10:34:24 +0100 (BST)
Message-ID: <5163E09F.4060105@cisco.com>
Date: Tue, 09 Apr 2013 10:34:23 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Scott Mansfield <scott.mansfield@ericsson.com>
References: <EF35EE4B92789843B1DECBC0E24558642195ED@eusaamb105.ericsson.se>
 <5163C1DF.1080006@cisco.com>
 <EF35EE4B92789843B1DECBC0E2455864219FE2@eusaamb105.ericsson.se>
In-Reply-To: <EF35EE4B92789843B1DECBC0E2455864219FE2@eusaamb105.ericsson.se>
Content-Type: multipart/alternative;
 boundary="------------000907090609060609030206"
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>,
 "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls] MPLS related liaison from ITU-T SG15
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>,
 <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
 <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 09:34:30 -0000

This is a multi-part message in MIME format.
--------------000907090609060609030206
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

So I believe the correct response is:

Thank you for your liaison.

Please can you make the text of these documents available to the IETF in 
sufficient time that members of the IETF who are not also members of the 
ITU can pass any review comments that they have to IETF colleagues who 
are members of the ITU for possible incorporation into their own review 
comments.

- Stewart



On 09/04/2013 09:37, Scott Mansfield wrote:
>
> The liaison is simply listing the documents that will be considered at 
> the meeting.  The text will be available about 1 month before the 
> meeting.  The text was not liaised, as the liaison states, the normal 
> ITU-T process will be used.  Which means that only members of the ITU 
> will have access to the text and have the ability to comment.  We can 
> try asking for access for non-ITU-T members if there is interest in 
> reviewing the documents.  We can exercise section 2.4 of RFC 6756 for 
> those that are not ITU-T members, but this will have to be done on a 
> case-by-case basis.
>
> Regards,
>
> -scott.
>
> *From:*Stewart Bryant [mailto:stbryant@cisco.com]
> *Sent:* Tuesday, April 09, 2013 3:23 AM
> *To:* Scott Mansfield
> *Cc:* mpls@ietf.org; ccamp@ietf.org; pwe3@ietf.org
> *Subject:* Re: [mpls] MPLS related liaison from ITU-T SG15
>
> On 09/04/2013 06:43, Scott Mansfield wrote:
>
>     Please see the informational liaison
>     http://datatracker.ietf.org/liaison/1249/
>     <http://datatracker.ietf.org/liaison/1249/> from the ITU-T SG15.
>
>     The liaison provides a list of the new and revised MPLS-TP related
>     documents that will enter the approval process at the next SG15
>     plenary meeting (1-15 July 2013).
>
>     Regards,
>
>     -scott.
>
>     Scott Mansfield
>
>     Ericsson Inc.
>
>     +1 724 931 9316
>
>
>
>
>     _______________________________________________
>
>     mpls mailing list
>
>     mpls@ietf.org  <mailto:mpls@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/mpls
>
> Scott, I see a list of document names, but no document text to review.
>
> Stewart
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--------------000907090609060609030206
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">So I believe the correct response is:<br>
      <br>
      Thank you for your liaison.<br>
      <br>
      Please can you make the text of these documents available to the
      IETF in sufficient time that members of the IETF who are not also
      members of the ITU can pass any review comments that they have to
      IETF colleagues who are members of the ITU for possible
      incorporation into their own review comments.<br>
      <br>
      - Stewart<br>
      <br>
      <br>
      <br>
      On 09/04/2013 09:37, Scott Mansfield wrote:<br>
    </div>
    <blockquote
      cite="mid:EF35EE4B92789843B1DECBC0E2455864219FE2@eusaamb105.ericsson.se"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Consolas","serif";
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D">The liaison is
            simply listing the documents that will be considered at the
            meeting.&nbsp; The text will be available about 1 month before
            the meeting.&nbsp; The text was not liaised, as the liaison
            states, the normal ITU-T process will be used.&nbsp; Which means
            that only members of the ITU will have access to the text
            and have the ability to comment.&nbsp; We can try asking for
            access for non-ITU-T members if there is interest in
            reviewing the documents.&nbsp; We can exercise section 2.4 of RFC
            6756 for those that are not ITU-T members, but this will
            have to be done on a case-by-case basis.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">-scott.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                Stewart Bryant [<a class="moz-txt-link-freetext" href="mailto:stbryant@cisco.com">mailto:stbryant@cisco.com</a>]
                <br>
                <b>Sent:</b> Tuesday, April 09, 2013 3:23 AM<br>
                <b>To:</b> Scott Mansfield<br>
                <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:ccamp@ietf.org">ccamp@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>
                <b>Subject:</b> Re: [mpls] MPLS related liaison from
                ITU-T SG15<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <div>
          <p class="MsoNormal">On 09/04/2013 06:43, Scott Mansfield
            wrote:<o:p></o:p></p>
        </div>
        <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
          <p class="MsoNormal">&nbsp;<o:p></o:p></p>
          <p class="MsoNormal">Please see the informational liaison <a
              moz-do-not-send="true"
              href="http://datatracker.ietf.org/liaison/1249/">
              http://datatracker.ietf.org/liaison/1249/</a> from the
            ITU-T SG15.<o:p></o:p></p>
          <p class="MsoNormal">The liaison provides a list of the new
            and revised MPLS-TP related documents that will enter the
            approval process at the next SG15 plenary meeting (1-15 July
            2013).<o:p></o:p></p>
          <p class="MsoNormal">&nbsp;<o:p></o:p></p>
          <p class="MsoNormal">Regards,<o:p></o:p></p>
          <p class="MsoNormal">-scott.<o:p></o:p></p>
          <p class="MsoNormal">&nbsp;<o:p></o:p></p>
          <p class="MsoNormal">Scott Mansfield<o:p></o:p></p>
          <p class="MsoNormal">Ericsson Inc.<o:p></o:p></p>
          <p class="MsoNormal">+1 724 931 9316<o:p></o:p></p>
          <p class="MsoNormal">&nbsp;<o:p></o:p></p>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              <br>
              <br>
              <o:p></o:p></span></p>
          <pre>_______________________________________________<o:p></o:p></pre>
          <pre>mpls mailing list<o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="mailto:mpls@ietf.org">mpls@ietf.org</a><o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/mpls">https://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></pre>
        </blockquote>
        <p class="MsoNormal"><span
            style="font-size:12.0pt;font-family:&quot;Times New
            Roman&quot;,&quot;serif&quot;">Scott, I see a list of
            document names, but no document text to review.<br>
            <br>
            Stewart<o:p></o:p></span></p>
      </div>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------000907090609060609030206--
