IETF Logo Mail Archive

Re: [Rtg-ooam-dt] How to better engage SFC?

Dave Dolson <ddolson@sandvine.com> Wed, 29 June 2016 22:03 UTC

Return-Path: <ddolson@sandvine.com>
X-Original-To: rtg-ooam-dt@ietfa.amsl.com
Delivered-To: rtg-ooam-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81F8212D843 for <rtg-ooam-dt@ietfa.amsl.com>; Wed, 29 Jun 2016 15:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.346
X-Spam-Level:
X-Spam-Status: No, score=-3.346 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=no
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 nB_mr5i1ZspK for <rtg-ooam-dt@ietfa.amsl.com>; Wed, 29 Jun 2016 15:03:05 -0700 (PDT)
Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DE1812D09F for <rtg-ooam-dt@ietf.org>; Wed, 29 Jun 2016 15:03:03 -0700 (PDT)
Received: from BLR-EXCHP-2.sandvine.com (192.168.196.172) by WTL-EXCHP-2.sandvine.com (192.168.194.177) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 29 Jun 2016 18:03:01 -0400
Received: from WTL-EXCHP-2.sandvine.com ([fe80::68ac:f071:19ff:3455]) by blr-exchp-2.sandvine.com ([fe80::6c6d:7108:c63c:9055%14]) with mapi id 14.03.0294.000; Wed, 29 Jun 2016 18:03:01 -0400
From: Dave Dolson <ddolson@sandvine.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it>, Erik Nordmark <nordmark@sonic.net>, "rtg-ooam-dt@ietf.org" <rtg-ooam-dt@ietf.org>, 'Alia Atlas' <akatlas@gmail.com>
Thread-Topic: [Rtg-ooam-dt] How to better engage SFC?
Thread-Index: AQHR0UsFckk1VOhC5EKwuGQZKQclOqAAaN6AgAC3aID//+ElRg==
Date: Wed, 29 Jun 2016 22:03:01 +0000
Message-ID: <20160629220259.5697621.58583.94305@sandvine.com>
References: <7347100B5761DC41A166AC17F22DF11221AB9C05@eusaamb103.ericsson.se> <ed828c45-2964-0102-1530-5f9a5c5c9789@sonic.net> <eea738aa4d7e4a6a8d10231346c440e2@TELMBXC02BA020.telecomitalia.local>, <7347100B5761DC41A166AC17F22DF11221ABCCA0@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF11221ABCCA0@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-ooam-dt/lYGc82PBNm4KLUo5wkAjoYetMJU>
Cc: Tal Mizrahi <talmi@marvell.com>
Subject: Re: [Rtg-ooam-dt] How to better engage SFC?
X-BeenThere: rtg-ooam-dt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: List is used by the Routing Area Overlay OAM Design team for internal coordination and discussion <rtg-ooam-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-ooam-dt>, <mailto:rtg-ooam-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-ooam-dt/>
List-Post: <mailto:rtg-ooam-dt@ietf.org>
List-Help: <mailto:rtg-ooam-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-ooam-dt>, <mailto:rtg-ooam-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 22:03:07 -0000

Recall you asked me not to submit a document to SFC, since you wanted the design team to provide guidelines.
What should I look at now as guidelines?


From: Gregory Mirsky
Sent: Wednesday, June 29, 2016 3:53 PM
To: Fioccola Giuseppe; Erik Nordmark; rtg-ooam-dt@ietf.org; 'Alia Atlas'
Cc: Tal Mizrahi; Dave Dolson
Subject: RE: [Rtg-ooam-dt] How to better engage SFC?



Hi Giuseppe,

I think it would be interesting to discuss considering proposals that may be addressed using the marking method:

·         draft-browne-sfc-nsh-timestamp

·         draft-spv-ippm-monitor-implementation-services-kpi

Would you have contribution for the gap analysis document too? That would be absolutely great.



                Regards,

                                Greg



-----Original Message-----
From: Fioccola Giuseppe [mailto:giuseppe.fioccola@telecomitalia.it]
Sent: Wednesday, June 29, 2016 1:57 AM
To: Erik Nordmark; Gregory Mirsky; rtg-ooam-dt@ietf.org; 'Alia Atlas'
Cc: Tal Mizrahi; Dave Dolson (ddolson@sandvine.com)
Subject: R: [Rtg-ooam-dt] How to better engage SFC?



Hi Erik,

Yes It is a very good idea.

If all of us agree, we could detail the marking method application in the SFC scenario, by considering some use cases.



Regards,



Giuseppe



-----Messaggio originale-----

Da: Rtg-ooam-dt [mailto:rtg-ooam-dt-bounces@ietf.org] Per conto di Erik Nordmark

Inviato: martedì 28 giugno 2016 16:41

A: Gregory Mirsky; rtg-ooam-dt@ietf.org<mailto:rtg-ooam-dt@ietf.org>; 'Alia Atlas'

Cc: Tal Mizrahi; Dave Dolson (ddolson@sandvine.com<mailto:ddolson@sandvine.com>)

Oggetto: [Rtg-ooam-dt] How to better engage SFC?



On the OOAM call this morning a question was raised whether we should present anywhere than RTFWG.



I wonder whether having an OOAM presentation in SFC would help to get more interest and contributions from SFC.

(I don't think we need it for BIER and NOV3 since we seem to have sufficient engagement with those WGs.)



Thoughts?

    Erik



_______________________________________________

Rtg-ooam-dt mailing list

Rtg-ooam-dt@ietf.org<mailto:Rtg-ooam-dt@ietf.org>

https://www.ietf.org/mailman/listinfo/rtg-ooam-dt



Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.



This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

v2.23.0 | Report a Bug | By Email