Re: [Dime] WGLC #1 for draft-ietf-dime-rfc4006bis-02

<lionel.morand@orange.com> Wed, 26 April 2017 09:52 UTC

Return-Path: <lionel.morand@orange.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2A4312956B; Wed, 26 Apr 2017 02:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 eAywPKnxCJI0; Wed, 26 Apr 2017 02:52:57 -0700 (PDT)
Received: from relais-inet.orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 627D312950E; Wed, 26 Apr 2017 02:52:57 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 1AF6410052F; Wed, 26 Apr 2017 11:52:56 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.58]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id EF0A6180073; Wed, 26 Apr 2017 11:52:55 +0200 (CEST)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILM33.corporate.adroot.infra.ftgroup ([fe80::3881:fc15:b4b2:9017%19]) with mapi id 14.03.0319.002; Wed, 26 Apr 2017 11:52:55 +0200
From: lionel.morand@orange.com
To: "Gardella, Maryse (Nokia - FR/Nozay)" <maryse.gardella@nokia.com>, Yuval Lifshitz <ylifshitz@sandvine.com>, jouni korhonen <jouni.nospam@gmail.com>, "dime@ietf.org list" <dime@ietf.org>
CC: "draft-ietf-dime-rfc4006bis@ietf.org" <draft-ietf-dime-rfc4006bis@ietf.org>
Thread-Topic: WGLC #1 for draft-ietf-dime-rfc4006bis-02
Thread-Index: AQHStz/0xtfIAFLmj026SxMSVKtHV6HK77KAgArVW4CAAW3eAIAAAOiAgABBkNA=
Date: Wed, 26 Apr 2017 09:52:55 +0000
Message-ID: <706_1493200376_59006DF8_706_2499_1_6B7134B31289DC4FAF731D844122B36E0C0C5590@OPEXCLILM43.corporate.adroot.infra.ftgroup>
References: <FFB3377A-3F65-456E-8EFC-CBBA2B671566@gmail.com> <C43C255C7106314F8D13D03FA20CFE4970067FC2@wtl-exchp-1.sandvine.com> <HE1PR0701MB2857DFA685DE0BF54D44594FFC1E0@HE1PR0701MB2857.eurprd07.prod.outlook.com> <C43C255C7106314F8D13D03FA20CFE497007E282@wtl-exchp-1.sandvine.com> <HE1PR0701MB2857A8BFF736098917FE6C06FC110@HE1PR0701MB2857.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0701MB2857A8BFF736098917FE6C06FC110@HE1PR0701MB2857.eurprd07.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
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/dime/atxucvUxCIxPXqWjuvP5wJT7FZg>
Subject: Re: [Dime] WGLC #1 for draft-ietf-dime-rfc4006bis-02
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 09:53:00 -0000

Hi,

I don't think that the LS process is efficient enough for a WGLC, especially as multiple 3GPP groups are interested and meetings are hold after the current deadline.
The easiest way is to announce the WGLC on CT3/CT4 and SA5 mailing lists and let interested people react on the draft and send their comments on the dime mailing list.
I had an issue with my mail last week and I was not able to post on 3GPP mailing list. I will do it today.

I will also indicate that the WGLC period is de facto extended to let two weeks to 3GPP guys for reviews/comments.

Regards,

Lionel


> -----Message d'origine-----
> De : DiME [mailto:dime-bounces@ietf.org] De la part de Gardella, Maryse
> (Nokia - FR/Nozay)
> Envoyé : mercredi 26 avril 2017 09:52
> À : Yuval Lifshitz; jouni korhonen; dime@ietf.org list
> Cc : draft-ietf-dime-rfc4006bis@ietf.org
> Objet : Re: [Dime] WGLC #1 for draft-ietf-dime-rfc4006bis-02
> 
> Hi Yuval
> Thanks to volunteer for this!
> Regarding  the process I do not have the answer, may be Lionel could help? To
> me, he is the official contact for interaction with 3GPP on Diameter,
> 
> BR
> Maryse
> 
> -----Original Message-----
> From: Yuval Lifshitz [mailto:ylifshitz@sandvine.com]
> Sent: mercredi 26 avril 2017 09:48
> To: Gardella, Maryse (Nokia - FR/Nozay) <maryse.gardella@nokia.com>; jouni
> korhonen <jouni.nospam@gmail.com>; dime@ietf.org list <dime@ietf.org>
> Cc: draft-ietf-dime-rfc4006bis@ietf.org; Yuval Lifshitz <ylifshitz@sandvine.com>
> Subject: RE: WGLC #1 for draft-ietf-dime-rfc4006bis-02
> 
> I can try and draft the LS, and send it for review to this group, but not sure what
> would be the formal process for sending it to SA5?
> 
> Yuval
> 
> -----Original Message-----
> From: Gardella, Maryse (Nokia - FR/Nozay)
> [mailto:maryse.gardella@nokia.com]
> Sent: Tuesday, April 25, 2017 12:59 PM
> To: Yuval Lifshitz; jouni korhonen; dime@ietf.org list
> Cc: draft-ietf-dime-rfc4006bis@ietf.org
> Subject: RE: WGLC #1 for draft-ietf-dime-rfc4006bis-02
> 
> Dear Yuval and all,
> 
> Sounds a good idea to have an LS to 3GPP SA5 for their coming May meeting.
> Even though it would be too late to get feedback on this version (considering the
> 4/30/17 deadline), it would be valuable for them to be aware about the ongoing
> RFC4006 evolution.
> 
> BR
> Maryse
> 
> -----Original Message-----
> From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Yuval Lifshitz
> Sent: mardi 18 avril 2017 14:33
> To: jouni korhonen <jouni.nospam@gmail.com>; dime@ietf.org list
> <dime@ietf.org>
> Cc: draft-ietf-dime-rfc4006bis@ietf.org
> Subject: [ALU] Re: [Dime] WGLC #1 for draft-ietf-dime-rfc4006bis-02
> 
> (as one of the editors) I think the document is ready, and no further work is
> needed.
> 
> As part of the review process, would also suggest sending an LS to 3GPP SA5
> work group to get their feedback. As their charging related specifications (e.g.
> 3GP TS 32.299) are heavily based on RFC4006.
> 
> Yuval
> 
> -----Original Message-----
> From: jouni korhonen [mailto:jouni.nospam@gmail.com]
> Sent: Monday, April 17, 2017 9:01 AM
> To: dime@ietf.org list
> Cc: jouni.nospam@gmail.com; lionel.morand@orange.com; draft-ietf-dime-
> rfc4006bis@ietf.org
> Subject: WGLC #1 for draft-ietf-dime-rfc4006bis-02
> 
> Folks,
> 
> This email starts a 2 week WGLC #1 for draft-ietf-dime-rfc4006bis-02. The WGLC
> ends 4/30/17 23:59 pacific time.
> Submit your comments to issue tracker
> (https://trac.ietf.org/trac/dime/newticket) and to mailing list. If you think the
> document needs no work and is ready, express that also on the list. Silence does
> not count as acceptance.
> 
> - Jouni & Lionel
> 
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.