IETF Logo Mail Archive

Re: [spring] IETF 102 - SPRING meeting

"Dhanendra Jain (dhjain)" <dhjain@cisco.com> Thu, 28 June 2018 21:11 UTC

Return-Path: <dhjain@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2B6130F39 for <spring@ietfa.amsl.com>; Thu, 28 Jun 2018 14:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 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, URIBL_BLOCKED=0.001, 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 pHWZKijdvI28 for <spring@ietfa.amsl.com>; Thu, 28 Jun 2018 14:11:04 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15704130EA7 for <spring@ietf.org>; Thu, 28 Jun 2018 14:11:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20128; q=dns/txt; s=iport; t=1530220264; x=1531429864; h=from:to:subject:date:message-id:mime-version; bh=AaqUFSVyjgAqigzQlIRseFYCTn+3ERnjANfkGyn8Vo8=; b=P6Yx5Nm0XeFYqtU9EO/N0QPzoe1j5Wtr07x6fu/vJQyExvXKDnlgauxw gwiFwGWFo763o7y/vXhXpZi8JDJvhgeSTGDUgNgC6M3otZO9hxUPLRklW s3gc6FHNAXUYQ7G8kzfXkzaPuNgIQ3LAaOEYxqo2n859/P5OV3ciSJQlk g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DMAADDTTVb/4sNJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYJTdmJ/KAqDb4gEjD6CB5AVhQkUgWYLJYRHAheDAyE0GAECAQECAQECbRwMhTYBBiMKXgEIEQMBAisCBDAdCgQBEoMgAYEbZA+uS4IchFuDeYEfBYhtgVY/gTaCaIFBgVcBAQEBAYEqARIBNgkMglUxgiQCh0aBBYQBhRGHYQkChgCJFIFAhAeIBoorhycCERMBgSQdOGFxcBVlAYI+CYImiGSFPm8BjjSBH4EaAQE
X-IronPort-AV: E=Sophos;i="5.51,284,1526342400"; d="scan'208,217";a="135536414"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Jun 2018 21:11:03 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id w5SLB3nf003229 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 28 Jun 2018 21:11:03 GMT
Received: from xch-rcd-007.cisco.com (173.37.102.17) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 28 Jun 2018 16:11:02 -0500
Received: from xch-rcd-007.cisco.com ([173.37.102.17]) by XCH-RCD-007.cisco.com ([173.37.102.17]) with mapi id 15.00.1320.000; Thu, 28 Jun 2018 16:11:02 -0500
From: "Dhanendra Jain (dhjain)" <dhjain@cisco.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] IETF 102 - SPRING meeting
Thread-Index: AQHUDySEniPoE0yecUGmtQ0VudIRPQ==
Date: Thu, 28 Jun 2018 21:11:02 +0000
Message-ID: <B07D146B-8F93-48B6-9E27-B79505927733@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.b.0.180311
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.131.52]
Content-Type: multipart/alternative; boundary="_000_B07D146B8F9348B69E27B79505927733ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/rGraFdlgkqwUYLB6PRyglL1FOrY>
Subject: Re: [spring] IETF 102 - SPRING meeting
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2018 21:11:07 -0000

Hi Bruno,  Rob,

I would like to request presentation slots for below two:

Topic: Segment Routing Yang extensions for BGP.
https://tools.ietf.org/html/draft-dhjain-spring-bgp-sr-yang-00
Duration: 8 Minutes.

Topic:  Updates to the BGP Signaled SR Policies
https://tools.ietf.org/html/draft-ietf-idr-segment-routing-te-policy-03
Duration: 8 minutes.

Thanks,
Dhanendra.

From: spring <spring-bounces@ietf.org> on behalf of "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Date: Monday, June 18, 2018 at 3:30 AM
To: "spring@ietf.org" <spring@ietf.org>
Subject: [spring] IETF 102 - SPRING meeting


Hi all,



During IETF 102, the SPRING WG is currently scheduled to meet Monday 13:30-15:30. We have a two hours session.
https://datatracker.ietf.org/meeting/102/agenda.html


It is time start building the SPRING WG agenda for Montreal.

Please send your request for a presentation slot, indicating draft name, speaker, and desired duration (covering presentation and discussion), before Monday 2018-07-02  09:00 CET. Before is better.

If it is not the first presentation of a non-WG draft, please give a reason why it is required to have a new presentation slot.

A checklist is available on the wiki: https://trac.ietf.org/trac/spring/wiki/Checklist%20for%20presenting%20at%20a%20SPRING%20meeting



As we are meeting on Monday, please send your slides on time, before Sunday 18:00 local time. Earlier is better.


Thanks,
--Bruno, Rob

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

v2.23.0 | Report a Bug | By Email