IETF Logo Mail Archive

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

Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it> Mon, 04 July 2016 15:00 UTC

Return-Path: <giuseppe.fioccola@telecomitalia.it>
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 DE8FE12D12F for <rtg-ooam-dt@ietfa.amsl.com>; Mon, 4 Jul 2016 08:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.636
X-Spam-Level:
X-Spam-Status: No, score=-5.636 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 0ZEzPiMGBQtt for <rtg-ooam-dt@ietfa.amsl.com>; Mon, 4 Jul 2016 08:00:38 -0700 (PDT)
Received: from TELEDG001RM001.telecomitalia.it (teledg001rm001.telecomitalia.it [217.169.121.18]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36F8612D124 for <rtg-ooam-dt@ietf.org>; Mon, 4 Jul 2016 08:00:37 -0700 (PDT)
Received: from TELMBXA06RM001.telecomitalia.local (10.14.252.34) by TELEDG001RM001.telecomitalia.it (10.19.3.111) with Microsoft SMTP Server (TLS) id 14.3.266.1; Mon, 4 Jul 2016 17:00:34 +0200
Received: from TELMBXB02RM001.telecomitalia.local (10.14.252.27) by TELMBXA06RM001.telecomitalia.local (10.14.252.34) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 4 Jul 2016 17:00:34 +0200
Received: from TELMBXB02RM001.telecomitalia.local ([fe80::2845:411e:c732:e844]) by TELMBXB02RM001.telecomitalia.local ([fe80::2845:411e:c732:e844%20]) with mapi id 15.00.1178.000; Mon, 4 Jul 2016 17:00:34 +0200
From: Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, 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] R: How to better engage SFC?
Thread-Index: AQHR06eAkeKE9CqUWUysIKlsynnREaAIXtUg
Date: Mon, 04 Jul 2016 15:00:34 +0000
Message-ID: <d869ab6ecbf1464ca2626391890d23a1@TELMBXB02RM001.telecomitalia.local>
References: <7347100B5761DC41A166AC17F22DF11221AB9C05@eusaamb103.ericsson.se> <ed828c45-2964-0102-1530-5f9a5c5c9789@sonic.net> <eea738aa4d7e4a6a8d10231346c440e2@TELMBXC02BA020.telecomitalia.local> <7347100B5761DC41A166AC17F22DF11221ABCCA0@eusaamb103.ericsson.se> <6b5b1c05f045425b8fc41d2a04290c39@TELMBXC02BA020.telecomitalia.local> <7347100B5761DC41A166AC17F22DF11221ABDF09@eusaamb103.ericsson.se> <5490663f08e34e48b92ef939fd3cfb85@TELMBXB02RM001.telecomitalia.local> <7347100B5761DC41A166AC17F22DF11221ABE71B@eusaamb103.ericsson.se> <f873d53353c14c72871de0685722e0b7@TELMBXB02RM001.telecomitalia.local>
In-Reply-To: <f873d53353c14c72871de0685722e0b7@TELMBXB02RM001.telecomitalia.local>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.14.252.242]
x-ti-disclaimer: Disclaimer1
Content-Type: multipart/alternative; boundary="_000_d869ab6ecbf1464ca2626391890d23a1TELMBXB02RM001telecomit_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-ooam-dt/Jy5APFIaR_x05BGqb6wTn-cdsOs>
Cc: Tal Mizrahi <talmi@marvell.com>, "Dave Dolson (ddolson@sandvine.com)" <ddolson@sandvine.com>
Subject: [Rtg-ooam-dt] R: R: 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: Mon, 04 Jul 2016 15:00:43 -0000

Hi All,
You can find below the proposed text for the gap analysis document that we can discuss tomorrow:

3.2.2.1.  Passive PM in BIER
[I-D.mirsky-bier-pmmm-oam] describes how the Marking Method can be used in BIER domain over MPLS networks.

3.2.2.2.  Passive PM in NVO3
The Generic Protocol Extension for VXLAN [I-D.ietf-nvo3-vxlan-gpe], Generic Network Virtualization Encapsulation [I-D.ietf-nvo3-geneve], Generic UDP Encapsulation [I-D.draft-ietf-nvo3-gue] are just some examples of the new encapsulations to support network virtualization.
NVO3 PM would be used to probe the NV Edge to NV Edge tunnels and NV Edge entity status for a DC network.
The main requirement for Performance Management is to support measurement of per VNI frame loss, delay and delay variation between two NV Edge devices that support the same VNI within a given NVO3 domain. Alternate Marking Method [I-D.ietf-ippm-alt-mark] allows these metrics efficiently.
Marking Method has been discussed in NVO3 sessions, but there is no draft in the working group.

3.2.2.3.  Passive PM over SFP
In the SFC architecture SF, SFF, Classifier and NSH Proxy Agent are the elements that can incorporate the measurement agent functionality to support SFC performance measurement.
The required OAM Performance Measurement, as described in [I-D.ietf-sfc-oam-framework], highlight the capability to assess the monitoring at SF and SFF or a Set of SF/SFF, both in case of SFC-aware SF and SFC-unaware SF; the monitoring of SFP (and RSP) that comprises a set of SFs that may be ordered or unordered; the monitoring of the Classifiers operation and the monitoring of the SFC as a whole.
The Alternate Marking Method for passive performance monitoring can be used for all these cases .
Performance management functions involve measuring of packet loss, delay, delay variance and could be well performed by the marking method proposed in [I-D.ietf-ippm-alt-mark].


Best Regards,

Giuseppe

Da: Rtg-ooam-dt [mailto:rtg-ooam-dt-bounces@ietf.org] Per conto di Fioccola Giuseppe
Inviato: venerdì 1 luglio 2016 16:47
A: Gregory Mirsky; Erik Nordmark; rtg-ooam-dt@ietf.org; 'Alia Atlas'
Cc: Dave Dolson (ddolson@sandvine.com); Tal Mizrahi
Oggetto: [Rtg-ooam-dt] R: How to better engage SFC?

Hi Greg,
Nice, I will propose a paragraph by Tuesday.

Thanks,

Giuseppe

Da: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
Inviato: venerdì 1 luglio 2016 15:47
A: Fioccola Giuseppe; Erik Nordmark; 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: RE: [Rtg-ooam-dt] How to better engage SFC?

Hi Giuseppe,
I was thinking that it would be logical in the gap analysis with conclusion that allocating field for the marking in an overlay header enables use of such flexible measurement method in passive-like OAM manner.

                Regards,
                                Greg

From: Fioccola Giuseppe [mailto:giuseppe.fioccola@telecomitalia.it]
Sent: Friday, July 01, 2016 2:31 AM
To: Gregory Mirsky; Erik Nordmark; 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>)
Subject: R: [Rtg-ooam-dt] How to better engage SFC?

Hi Greg,
Excellent, we'll discuss the problems these drafts are addressing next Tuesday.

Regarding marking method application in SFC, what is you plan for now?
Is a contribution for the gap analysis document good for this goal? or are you thinking of a new draft as is in BIER?

Regards,

Giuseppe

Da: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
Inviato: giovedì 30 giugno 2016 21:28
A: Fioccola Giuseppe; Erik Nordmark; 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: RE: [Rtg-ooam-dt] How to better engage SFC?

Hi Giuseppe,
thank you for volunteering to help with PM story. It would be great to make it about the marking method in SFC pointing to flexibility of placing the Test Point either at Classifier, SF or SFF. And, as done in PM with the Marking Method in BIER Layer, demonstrate benefit of two-bit long vs. one-bit long field for marking.

As for the listed drafts I have serious concerns that I'll sum and share with the team before our meeting next Tuesday. I'd like to look not into particular solutions described in these drafts but for the problems they are addressing. I think these are real-life problems and we can propose solutions to, solutions based on Common Overlay OAM.

                Regards,
                                Greg

From: Fioccola Giuseppe [mailto:giuseppe.fioccola@telecomitalia.it]
Sent: Thursday, June 30, 2016 3:06 AM
To: Gregory Mirsky; Erik Nordmark; 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>)
Subject: R: [Rtg-ooam-dt] How to better engage SFC?

Hi Greg, All
That's for sure! I appreciate your consideration.
The documents you suggested are precious.
In particular, draft-browne-sfc-nsh-timestamp could be considered for the timestamping of NSH packets and be combined to the marking method very well.
The proposed extension to TWAMP to carry services KPI data, proposed in draft-spv-ippm-monitor-implementation-services-kpi, is also suitable for the purpose.
And draft-agv-sfc-performance-measurement-architecture should be the reference for the PM architecture for SFCs

If all of us agree, I could propose some text for the "PM over SFP" Section of the gap analysis document with reference to draft-ietf-ippm-alt-mark and documents quoted above.
I could send you proposed text before next Tuesday call.

Best Regards,

Giuseppe

Da: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
Inviato: mercoledì 29 giugno 2016 21:53
A: Fioccola Giuseppe; Erik Nordmark; 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: 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<mailto:rtg-ooam-dt@ietf.org>; 'Alia Atlas'
Cc: Tal Mizrahi; Dave Dolson (ddolson@sandvine.com<mailto: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