Re: [CCAMP] G.698.2 MIB concerns addressed by ITU-T colleagues
Huub van Helvoort <huubatwork@gmail.com> Sun, 16 March 2014 15:18 UTC
Return-Path: <huubatwork@gmail.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B9BD1A01E9 for <ccamp@ietfa.amsl.com>; Sun, 16 Mar 2014 08:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_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 inkwInLdQRQ5 for <ccamp@ietfa.amsl.com>; Sun, 16 Mar 2014 08:18:09 -0700 (PDT)
Received: from mail-ee0-x230.google.com (mail-ee0-x230.google.com [IPv6:2a00:1450:4013:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 854F21A01BE for <ccamp@ietf.org>; Sun, 16 Mar 2014 08:18:09 -0700 (PDT)
Received: by mail-ee0-f48.google.com with SMTP id b57so2517279eek.21 for <ccamp@ietf.org>; Sun, 16 Mar 2014 08:18:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=1yNbP3YeletZdY6NvkXhVW888e1FQ0RMm79Us1RytM8=; b=X7ej1PP21ctf0buEZfFXYzhNfyJUnTFCGFcxIqnM+M8mVK0HH5XP/b67xcrar2JzoL Js3b9wjBIE6lwrn22LnAs0NXIZdCLdTdF+zucdpxWgeauuC3vMIz8SAxNson69wjIkkQ MeEOqbo93l8He0FkKeopK1T+xJkaN41kNUgsYVFI0q2BVfuAB2Sj5qG6GVI4VqZVWAYs YUreu3/Kve27XVSud99TNwq9/xklXFPWiqBC7aKO8rSSdiytONBZe50jrlpWBk7UyJP3 Iq/xfpazCEyXx43QU/R/A3nSLjsMQXmUdjdOMyq8IOnIavixVqU2hCeE4QroS2S0n0UO C5lA==
X-Received: by 10.14.39.3 with SMTP id c3mr19052557eeb.42.1394983081490; Sun, 16 Mar 2014 08:18:01 -0700 (PDT)
Received: from McAsterix.local (g215085.upc-g.chello.nl. [80.57.215.85]) by mx.google.com with ESMTPSA id t4sm20460539eeb.29.2014.03.16.08.18.00 for <ccamp@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Mar 2014 08:18:00 -0700 (PDT)
Message-ID: <5325C0A8.9060100@gmail.com>
Date: Sun, 16 Mar 2014 16:18:00 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "ccamp@ietf.org" <ccamp@ietf.org>
References: <D0A3A22C2D7BE64AA7506612C2E9BAB7015368006C1B@HE101451.emea1.cds.t-internal.com> <532311C3.8050505@gmail.com> <06bde98852e5483394a446bdc62a5452@BN1PR05MB041.namprd05.prod.outlook.com>
In-Reply-To: <06bde98852e5483394a446bdc62a5452@BN1PR05MB041.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/TtjY9B9xe8femTNwXSFKm6OBduU
Subject: Re: [CCAMP] G.698.2 MIB concerns addressed by ITU-T colleagues
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Mar 2014 15:18:12 -0000
Hallo Gert, You wrote: > we go back and forth on this since quite a while. > As neither the LMP nor the SNMP draft are WG documents, > there is no Liaison. I was not aware of the requirement to have a WG document before being able to liaise. In that case only direct communication between the autors and Q6 experst remains. > Without Liaison we don't get official input from Q6 and need to > work with informal communication. What will you do if Q6 experts do not support your ideas? > My understanding is that Q6 doesn't have an issue with CCAMP > working on LMP but wants to review a parameter. My understanding is that they are concerned about using an application code with additional parameter values. This is in fact creating a new application code. > So technically we should be ready to accept this as a WG item > and use it as a basis for a Liaison with Q6. You asked the same question about accepting in the meeting I did not see much support. My 2p, Regards, Huub. > -----Original Message----- > From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of Huub van Helvoort > Sent: 14 March 2014 15:27 > To: ccamp@ietf.org > Subject: Re: [CCAMP] G.698.2 MIB concerns addressed by ITU-T colleagues > > Hallo Rüdiger, > > You wrote: > >> Huub and Dieter mentioned during the CAMP session in London that ITU-T >> Q6 has some concerns about additional values in document. > > It was indeed I who mentioned that. During conversations with Q6 experts I noticed that they have still concerns regarding the use of an application code and adding additional parameters because that defeats the intention to define and use application codes. > > My intent was to suggest that you communicate with Q6 experts either by attending Q6 meetings and submit contributions for discussion, or write a liaison from CCAMP to Q6 asking for their opinion regarding the drafts that were introduced in the CCAMP meeting. > >> Gabriele mentioned the reason for adding these values and we will >> update the documents with explaining text. > > I was only the messenger, it would be better to communicate directly with Q6 experts. > >> During our common meeting with ITU-T at IETF 86 Pete Anslow mentioned: > > Transmit power may be useful, beyond >> that I cannot think of anything else you may want to set. > > IETF86 is already some time ago. You could have asked in the meantime what Pete actually did mean by "may be useful". > >> If you guys have still concerns lets discuss these points on the list. > > Again: I am only the messenger, please talk to the Q6 experts directly. FYI Q6 is meeting in the week of March 23. > > Best regards, tschüss, Huub. > > > > > -- > ***************************************************************** > 请记住,你是独一无二的,就像其他每一个人一样 > > _______________________________________________ > CCAMP mailing list > CCAMP@ietf.org > https://www.ietf.org/mailman/listinfo/ccamp > -- ***************************************************************** 请记住,你是独一无二的,就像其他每一个人一样
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Fatai Zhang
- [CCAMP] G.698.2 MIB concerns addressed by ITU-T c… RKunze
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Dieter Beller
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Gabriele Maria Galimberti (ggalimbe)
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Fatai Zhang
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… John E Drake
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… John E Drake
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Huub van Helvoort
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Gert Grammel
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Huub van Helvoort
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Lou Berger
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Fatai Zhang
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Gabriele Maria Galimberti (ggalimbe)
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Gert Grammel
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Gabriele Maria Galimberti (ggalimbe)
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… John E Drake
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Fatai Zhang
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Gert Grammel
- Re: [CCAMP] G.698.2 MIB concerns addressed by ITU… Fatai Zhang