Re: [mpls] Comments on draft-bryant-mpls-oam-udp-return
"MORTON, ALFRED C (AL)" <acmorton@att.com> Fri, 23 May 2014 17:14 UTC
Return-Path: <acmorton@att.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF49A1A073F for <mpls@ietfa.amsl.com>; Fri, 23 May 2014 10:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001] autolearn=ham
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 S15WA28kiN8a for <mpls@ietfa.amsl.com>; Fri, 23 May 2014 10:13:59 -0700 (PDT)
Received: from mail-red.research.att.com (mail-red.research.att.com [204.178.8.23]) by ietfa.amsl.com (Postfix) with ESMTP id 347381A06DF for <mpls@ietf.org>; Fri, 23 May 2014 10:13:59 -0700 (PDT)
Received: from mail-blue.research.att.com (unknown [135.207.178.11]) by mail-red.research.att.com (Postfix) with ESMTP id 3B7DE554C52; Fri, 23 May 2014 13:15:56 -0400 (EDT)
Received: from njfpsrvexg8.research.att.com (unknown [135.207.255.243]) by mail-blue.research.att.com (Postfix) with ESMTP id 56D63F03A0; Fri, 23 May 2014 13:13:57 -0400 (EDT)
Received: from NJFPSRVEXG8.research.att.com ([fe80::cdea:b3f6:3efa:1841]) by njfpsrvexg8.research.att.com ([fe80::cdea:b3f6:3efa:1841%13]) with mapi; Fri, 23 May 2014 13:13:57 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Eric Gray <eric.gray@ericsson.com>, "stbryant@cisco.com" <stbryant@cisco.com>, Gregory Mirsky <gregory.mirsky@ericsson.com>, "draft-bryant-mpls-oam-udp-return@tools.ietf.org" <draft-bryant-mpls-oam-udp-return@tools.ietf.org>
Date: Fri, 23 May 2014 13:13:55 -0400
Thread-Topic: [mpls] Comments on draft-bryant-mpls-oam-udp-return
Thread-Index: AQHPdQcJZ0y8Hhq70US8I/RdC07quZtM1WrpgABV0wCAAEhlgIAAtT8AgABknID//71acIAAG3vg
Message-ID: <2845723087023D4CB5114223779FA9C8017992C1F2@njfpsrvexg8.research.att.com>
References: <7347100B5761DC41A166AC17F22DF1121B79D6DE@eusaamb103.ericsson.se> <534535F8.6090408@cisco.com> <48E1A67CB9CA044EADFEAB87D814BFF632A54011@eusaamb107.ericsson.se> <537CC24A.2020803@cisco.com> <7347100B5761DC41A166AC17F22DF1121B7C0A12@eusaamb103.ericsson.se> <537E2DD7.4020901@cisco.com> <7347100B5761DC41A166AC17F22DF1121B7C0FCE@eusaamb103.ericsson.se> <537E7A53.50707@cisco.com> <48E1A67CB9CA044EADFEAB87D814BFF632AC1052@eusaamb107.ericsson.se> <537F66C3.4070203@cisco.com> <48E1A67CB9CA044EADFEAB87D814BFF632AC1249@eusaamb107.ericsson.se>
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF632AC1249@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/6ayUgkTTzpm2vb4c7EoImNKo0t8
Cc: "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-lmap-framework@tools.ietf.org" <draft-ietf-lmap-framework@tools.ietf.org>
Subject: Re: [mpls] Comments on draft-bryant-mpls-oam-udp-return
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: <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: Fri, 23 May 2014 17:14:00 -0000
Eric, Stewart, It seems to me (after scanning the draft) that the MPLS-PLDM could be treated as the out-of-scope measurement traffic/protocol in the LMAP Framework Figure 1 below (Where IPPM is currently used as the out-of-scope example): ^ | Active +-------------+ IPPM +---------------+ Measurement | Measurement | Scope | Measurement |<------------>| Peer | | | Agent | Traffic +-------------+ v +------->| | ^ | +---------------+ | | ^ | | | Instruction | | Report | | | +-----------------+ | | | | | | | v LMAP | +------------+ +------------+ Scope | | Controller | | Collector | | | +------------+ +------------+ v | ^ ^ | ^ | | | | | | | +----------+ | | | | | v | +------------+ +----------+ +--------+ +----------+ | |Bootstrapper| |Subscriber|--->| data |<---|repository| Out +------------+ |parameter | |analysis| +----------+ of |database | | tools | Scope +----------+ +--------+ | | The MPLS-PLDM Querier could be co-located with a Measurement Agent, and assuming the Querier performs all the coordination, including arranging to return the response message to a port co-located with the same Measurement Agent (or configuration takes the role of signaling), then the MPLS-PLDM responder could be treated as a Measurement Peer. The LMAP Control and Report protocols provision and collect results from the Querier, taking the role of a "management system" mentioned in the draft. hope this helps, Al > -----Original Message----- > From: Eric Gray [mailto:eric.gray@ericsson.com] > Sent: Friday, May 23, 2014 11:47 AM > To: stbryant@cisco.com; Gregory Mirsky; draft-bryant-mpls-oam-udp- > return@tools.ietf.org > Cc: mpls@ietf.org; draft-ietf-lmap-framework@tools.ietf.org > Subject: RE: [mpls] Comments on draft-bryant-mpls-oam-udp-return > > Stewart, > > I understand your point. But the question is not whether or not it > will work, > but rather whether or not there is consensus to do it this way. > > On any given day, it is trivial to come up with any number of > approaches > for doing something (whatever that something is) that will _work_ - which > is not the > same as saying that we should all pour energy into any of those ideas. > > I also understand the pressures associated with customer > requirements, but > don't see why the customer(s) behind your requirements should have the > last word > on which approach should be used - based solely on those requirements. > > That approach leads to a point-solution that has a definite non-zero > cost. As > a general approach, the continuous generation of point solutions has its > own scaling > issues. > > It is my hope that someone will have the energy to put together a > draft to > propose an alternative based on LMAP. I personally do not have either the > energy > or the bandwidth. In fact, I don't have the bandwidth or the energy to > continue in > this discussion. I sincerely hope and intend this will be my last post > on this topic. > > If there is insufficient interest in developing the scaled-down > version of an > LMAP-based proposal - either within the MPLS working group, or among the > LMAP > framework authors - before the Toronto meeting, or there is not a number > of like > objections raised on the MPLS mailing list, then it would seem that the WG > default > consensus is to proceed with your draft. > > Believe it or not, I personally can live with that. > > -- > Eric > > -----Original Message----- > From: Stewart Bryant [mailto:stbryant@cisco.com] > Sent: Friday, May 23, 2014 11:18 AM > To: Eric Gray; Gregory Mirsky; draft-bryant-mpls-oam-udp- > return@tools.ietf.org > Cc: mpls@ietf.org; draft-ietf-lmap-framework@tools.ietf.org > Subject: Re: [mpls] Comments on draft-bryant-mpls-oam-udp-return > Importance: High > > Eric > > I think the onus is on you as the objector to provide me with a pointer to > a specific protocol alternative not a framework, or to show why this > simple addition of four bytes will not work in the manner that I describe. > > Stewart
- [mpls] Comments on draft-bryant-mpls-oam-udp-retu… Gregory Mirsky
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Stewart Bryant
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Eric Gray
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Stewart Bryant
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Gregory Mirsky
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Eric Gray
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Stewart Bryant
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Loa Andersson
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Loa Andersson
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Stewart Bryant
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Stewart Bryant
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Stewart Bryant
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Gregory Mirsky
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Stewart Bryant
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Gregory Mirsky
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Stewart Bryant
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Eric Gray
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Stewart Bryant
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Eric Gray
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… MORTON, ALFRED C (AL)
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Gregory Mirsky
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Stewart Bryant
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Gregory Mirsky
- Re: [mpls] Comments on draft-bryant-mpls-oam-udp-… Andrew G. Malis