Re: [mpls] MPLS requests for IETF 102
"Tarek Saad (tsaad)" <tsaad@cisco.com> Sun, 01 July 2018 15:03 UTC
Return-Path: <tsaad@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 B750F130934; Sun, 1 Jul 2018 08:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZX52-hEsTSP; Sun, 1 Jul 2018 08:03:42 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4C8D12F1A6; Sun, 1 Jul 2018 08:03:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21467; q=dns/txt; s=iport; t=1530457422; x=1531667022; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=pAps9GFd2/PtyD60mEf0rqKvr/Fh7s4aZcrmJaQo+Gk=; b=JCsbyIr9iK6ve5rJAIx2FubRJVcqt3jZRi9cBXIoNpMt/OSPHGzB4M3w KVds2opBZ6wb8Nxd600Ij0gB5x9NzTJYxNRCXXj7fe7N3ILdg9hVUJaLs XxfIGRL4XDSTdmo+QbiTeMWAGqPTNSVwDZmcaQ0c06Vk6CNBVibtaqTX3 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BeAwA37Dhb/49dJa1cGQEBAQEBAQEBAQEBAQcBAQEBAYJTSC5ifygKg2+UP4IHkBiFIIFmCyOESQIXgwshOBQBAgEBAgEBAm0cAQtCEAGEYwEBAQEDI0gDCw4CAgEIEQMBAisCAgIZFx0IAgQOBQ6DEgGBfw+nfoIchFuDbIEfCgUFiGiBVj+BDyeCaIFBgVcCAQKBKgESASURCYJhMYIkAohMhAI7jD0JAoNYgiyJF4FAhAyICYozhy0CERMBgSQ0IWFxcBU7KgGCPgmCJ4hkhT5vAYsMgyGBH4EaAQE
X-IronPort-AV: E=Sophos;i="5.51,295,1526342400"; d="scan'208,217";a="136594275"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jul 2018 15:03:41 +0000
Received: from XCH-RTP-001.cisco.com (xch-rtp-001.cisco.com [64.101.220.141]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id w61F3eMT020058 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 1 Jul 2018 15:03:40 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-001.cisco.com (64.101.220.141) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sun, 1 Jul 2018 11:03:40 -0400
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1320.000; Sun, 1 Jul 2018 11:03:39 -0400
From: "Tarek Saad (tsaad)" <tsaad@cisco.com>
To: "mpls@ietf.org" <mpls@ietf.org>
CC: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Thread-Topic: MPLS requests for IETF 102
Thread-Index: AQHUBwzGp39pdnmY1kWXEGPIXrXluqR6i0cA
Date: Sun, 01 Jul 2018 15:03:39 +0000
Message-ID: <7A3FD20C-C803-4E63-A3D3-449C269C8294@cisco.com>
References: <88D25496-1058-4FD0-A31A-C101B026C21F@cisco.com>
In-Reply-To: <88D25496-1058-4FD0-A31A-C101B026C21F@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.240.129]
Content-Type: multipart/mixed; boundary="_004_7A3FD20CC8034E63A3D3449C269C8294ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/CS-VQGIQRWalhvkt_Z73jJYgmdY>
Subject: Re: [mpls] MPLS requests for IETF 102
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 01 Jul 2018 15:03:45 -0000
Hi all, This is a reminder to send out the requests for presentation slots @ MPLS WG session in Montreal and/or the status report if not presenting. Also, please see the email from Loa attached. Regards, Tarek From: Tarek Saad <tsaad@cisco.com> Date: Monday, June 18, 2018 at 10:01 AM To: "mpls@ietf.org" <mpls@ietf.org> Cc: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org> Subject: MPLS requests for IETF 102 Resent-From: <alias-bounces@ietf.org> Resent-To: Tarek Saad <tsaad@cisco.com>, <n.leymann@telekom.de>, <loa@pi.nu> Resent-Date: Monday, June 18, 2018 at 10:01 AM Hi all, We are building the MPLS WG session’s agenda for IETF102 in Montreal. The preliminary agenda for IETF102, is available at: https://datatracker.ietf.org/meeting/102/agenda.html The MPLS WG session is currently scheduled for: Tuesday, July 17, 2018 (EDT), 9:30-12:00 Morning session I Please send slot requests for presenting at the MPLS session copying myself and the WG chairs - indicate draft name, speaker and desired duration. If presenting, your slides will be due by Friday July 13th. Please send slides to myself and the WG chairs. A reminder to authors/editors of MPLS WG drafts that will not be discussed/presented at IET102 to send a status report to the WG list by Friday March 13th so it can be included in the MPLS WG progress report. Regards, Tarek and MPLS WG chairs
--- Begin Message ---Working Group, Among other things that we want to do at f2f meetings is to capture the status of our working group documents. We have procedure we have been running for a number of years, but there are new authors/participants, so this is a reminder. At a f2f meeting, like the upcoming meeting in Montreal in July, working groups drafts are always on the agenda. There are at least two different ways this can happen. - the document can be put on the agenda for discussion -- the authors might have things they believe is best discussed in a f2f meeting -- the chairs might request that the authors discusses certain open issues at the f2f meeting - the document might appear in the chairs status report -- this normally happens if there is nothing that needs to be discussed in the f2f meeting. In this case the authors are required to send a short report to be included in the status report, for example "we have sorted out all the issues brought up on the mailing list and earlier discussions, we are now ready for wglc", would be a proper input for such a report. In the case the report gets substantially longer or more complicated it is likely the chairs will encourage the authors to bring it up in the f2f meeting. Tarek will send out reminders to the authors of wg document 2-3 weeks before the meeting. /Loa for the mpls wg co-chairs -- Loa Andersson email: loa@pi.nu Senior MPLS Expert Bronze Dragon Consulting phone: +46 739 81 21 64--- End Message ---
- [mpls] MPLS requests for IETF 102 Tarek Saad (tsaad)
- Re: [mpls] MPLS requests for IETF 102 Adrian Farrel
- Re: [mpls] MPLS requests for IETF 102 Andrew G. Malis
- Re: [mpls] MPLS requests for IETF 102 Tarek Saad (tsaad)
- Re: [mpls] MPLS requests for IETF 102 Tarek Saad (tsaad)
- Re: [mpls] MPLS requests for IETF 102 Lizhenbin
- Re: [mpls] MPLS requests for IETF 102 Loa Andersson
- Re: [mpls] MPLS requests for IETF 102 Andrew G. Malis