Re: [PMOL] FW: [IPPM] FWD: LIAISON STATEMENT FROM THE BROADBAND FORUM

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 05 September 2012 11:33 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: pmol@ietfa.amsl.com
Delivered-To: pmol@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79D6721F865E for <pmol@ietfa.amsl.com>; Wed, 5 Sep 2012 04:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.81
X-Spam-Level:
X-Spam-Status: No, score=-103.81 tagged_above=-999 required=5 tests=[AWL=-0.289, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SUBJ_ALL_CAPS=2.077, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jA1IEeEqyhWm for <pmol@ietfa.amsl.com>; Wed, 5 Sep 2012 04:33:06 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id E06A921F865D for <pmol@ietf.org>; Wed, 5 Sep 2012 04:33:05 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGo3R1DGmAcF/2dsb2JhbAA7CrscdxCCIAEBAQEDEgoRA0kQAgEIDQEDAQMBAQsGDAsBBgFFAwUBCAEBBAESCBqHawudIJ0rBIsRCgYKCIYAYAObWooZgmWBXw
X-IronPort-AV: E=Sophos; i="4.80,374,1344225600"; d="scan'208,217"; a="323515574"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 05 Sep 2012 07:29:04 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 05 Sep 2012 07:26:34 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD8B5A.3503A8D8"
Date: Wed, 05 Sep 2012 13:33:00 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04080C142B@307622ANEX5.global.avaya.com>
In-Reply-To: <201209041320.q84DKuw9024588@alpd052.aldc.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PMOL] FW: [IPPM] FWD: LIAISON STATEMENT FROM THE BROADBAND FORUM
Thread-Index: Ac2KoNP6tRO30S4ORz+XPGTqo7QAJQAuJtjg
References: <07F7D7DED63154409F13298786A2ADC9045627F6@EXRAD5.ad.rad.co.il> <201209041320.q84DKuw9024588@alpd052.aldc.att.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Al Morton <acmorton@att.com>, Yaakov Stein <yaakov_s@rad.com>, pmol@ietf.org
Cc: Ronald Bonica <rbonica@juniper.net>
Subject: Re: [PMOL] FW: [IPPM] FWD: LIAISON STATEMENT FROM THE BROADBAND FORUM
X-BeenThere: pmol@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Performance Metrics Directorate list <pmol.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pmol>, <mailto:pmol-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pmol>
List-Post: <mailto:pmol@ietf.org>
List-Help: <mailto:pmol-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pmol>, <mailto:pmol-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 11:33:08 -0000

Hi Al,

I would let our (OPS) ADs decide together with the Transport ADs
sponsoring IPPM who is to be charged with drawing a response. 

One question - you wrote: 

*	IMO, the next steps are to agree on a test architecture and
divide the work of metric definition, methods of measurement, 
and supporting protocol development among SDOs

Do you believe that there is a need for new protocol development for BB
access performance? 

Regards,

Dan


		_____________________________________________
		From: pmol-bounces@ietf.org
[mailto:pmol-bounces@ietf.org] On Behalf Of Al Morton
		Sent: Tuesday, September 04, 2012 4:20 PM
		To: Yaakov Stein; pmol@ietf.org
		Subject: MCAFEE E-MAIL SCAN ALERT!~RE: [PMOL] FW: [IPPM]
FWD: LIAISON STATEMENT FROM THE BROADBAND FORUM
		

		
		Attachment file :
bbf2012.1068.01.Liaison_to_IEEE__IETF__and_ITU_Regarding_WT-304_Status.d
oc\3.OLE
		Scanner Detected: Suspicious Extensions (Virus)
		Action taken : No Action Taken (File has a multiple
extension) 
		
		
		At 10:33 AM 9/3/2012, Yaakov Stein wrote:

				Although I am sure that most of you have
already seen this message, 
				I am forwarding it, because I believe
that this liaison function should be the responsibility of the
performance directorate.
		
			Interesting possibility.  I can certainly
imagine members of 
			the Directorate commenting on this liaison, but
why would we
			claim responsibility for development of a reply?
			
			IMO, the next steps are to agree on a test
architecture and
			divide the work of metric definition, methods of
measurement, 
			and supporting protocol development among SDOs,
where the 
			first step is to package existing standards that
are relevant 
			and identify new standards development needed.
			
			Some background on this Liaison:
			
			The current text:
			https://datatracker.ietf.org/liaison/1179/
			is the first of two liaisons from BBF.  There is
a more recent
			liaison from BBF's meeting last week which has
not found its way 
			statements@ietf.org yet.  (I just forwarded it
myself, attached.)
			The response should be to the combination of
both liaisons (now that 
			there are two), not the first alone.  David
Sinicrope <mailto:david.sinicrope@ericsson.com> 
			is IETF's Liaison Manager with BBF.
			
			Apparently (second-hand info from a BBF
attendee), the FCC has sent
			a letter to both the BBF and the IETF requesting
the development
			of industry standards for broadband performance
measurement,
			and the FCC letter was discussed at BBF last
week.
			*Russ or someone in IETF/IAB should have
received that letter.*
			I don't have a copy.
			
			Ron Bonica has asked for comments on the first
liaison on ietf@ietf.
			Some questions were raised among IPPM folks
after Matt Z forwarded
			Ron's request on ippm-list.
			
			Finally, ITU-T SG 12 prepared an informative
reply to the first 
			BBF liaison last June (also attached).
			
			Al
			
		
		
		 << File:
bbf2012.1068.01.Liaison_to_IEEE__IETF__and_ITU_Regarding_WT-304_Status.d
oc >>  << File: T09-SG12-120529-TD-GEN-0875!r1!!MSW-E.doc >>  << File:
ATT1826957.txt >>