Re: [Softwires] ISP CGN logging inc. Destination ??

<mohamed.boucadair@orange.com> Mon, 07 May 2018 11:19 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E217126B6E; Mon, 7 May 2018 04:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 4WEqL7zn-mfL; Mon, 7 May 2018 04:19:14 -0700 (PDT)
Received: from 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 036631200C1; Mon, 7 May 2018 04:19:14 -0700 (PDT)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id DBD8F10028C; Mon, 7 May 2018 13:19:12 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id ACCB680062; Mon, 7 May 2018 13:19:12 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM5D.corporate.adroot.infra.ftgroup ([fe80::9898:741c:bc1d:258d%19]) with mapi id 14.03.0389.001; Mon, 7 May 2018 13:19:12 +0200
From: mohamed.boucadair@orange.com
To: "Ramesh.R.Chandra@ril.com" <Ramesh.R.Chandra@ril.com>, "ianfarrer@gmx.com" <ianfarrer@gmx.com>, "rajiva@cisco.com" <rajiva@cisco.com>
CC: "softwires@ietf.org" <softwires@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Softwires] ISP CGN logging inc. Destination ??
Thread-Index: AQHT4yi6QsPwS4mEj0Wx5sa9RJtTQaQe3eyAgAAdZICAACCTAIAAfGTggASI/LA=
Date: Mon, 07 May 2018 11:19:12 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DF15558@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <56C7D96E-182F-4584-B190-DCD17957C01F@cisco.com> <95081DF2-FBE4-4B28-802E-13988B6DDF8D@gmx.com> <8433F1DD-3988-4DF6-B14D-3873B0F36CCB@cisco.com> <DE94262F-6C94-492A-B9F0-629160527B37@gmx.com> <ef2bbe951814477eae919a4abf9ae182@SHYDEXMBX08.in.ril.com>
In-Reply-To: <ef2bbe951814477eae919a4abf9ae182@SHYDEXMBX08.in.ril.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.2]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/EFN3TcQGsbMPT7AONPGxxgpTdYg>
Subject: Re: [Softwires] ISP CGN logging inc. Destination ??
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2018 11:19:16 -0000

Dear Ramesh,

Please see inline. 

Cheers,
Med

> -----Message d'origine-----
> De : Softwires [mailto:softwires-bounces@ietf.org] De la part de
> Ramesh.R.Chandra@ril.com
> Envoyé : vendredi 4 mai 2018 17:26
> À : ianfarrer@gmx.com; rajiva@cisco.com
> Cc : softwires@ietf.org; int-area@ietf.org
> Objet : Re: [Softwires] ISP CGN logging inc. Destination ??
> 
> Dear Ian,  thanks for clarifications.
> 
> Regulator in India mandated to preserve the following details for each flow.
> 1.	Source IP + Port (private for end subscriber device)

[Med] Please note that this one may be overlapping among multiple subscribers if DS-Lite is used. 

> 2.	Destination IP + Port (public)

[Med] Does the regulator require to preserve "Destination IP + Port" even if a public IP address is assigned to a subscriber?

> 3.	Translated IP + port (public)
> 4.	Date and time
> 
> There is no brainer and all this is available in NAT44. MAP being stateless,
> no such data available from MAP-BR. We are exploring alternate option on BR
> to create this data in MAP.
> 
> Pls advise.
> 
> Regds
> ramesh
> -----Original Message-----
> From: ianfarrer@gmx.com [mailto:ianfarrer@gmx.com]
> Sent: 04 May 2018 17:28
> To: Rajiv Asati (rajiva)
> Cc: Softwires-wg list; int-area@ietf.org; Ramesh R Chandra
> Subject: Re: [Softwires] ISP CGN logging inc. Destination ??
> 
> Hi Rajiv,
> 
> Please see inline.
> 
> Cheers,
> Ian
> 
> > On 4. May 2018, at 12:01, Rajiv Asati (rajiva) <rajiva@cisco.com> wrote:
> >
> > Ian,
> >
> > Thanks for sharing the URL. While not explicit, “all metadata” would
> include both source and destination A+P. Is that the right interpretation?
> 
> [if - My understanding is that per-flow logging is necessary to meet the
> requirement, but I’m not familiar enough with the legislation to know what
> exactly needs to be stored.]
> 
> >
> > If an ISP were to use “binding” mode on the BR, then without using net
> flow/IPFIX, How could the compliance be achieved ?
> 
> [if - If there’s address sharing and the requirement is to provide an exact
> match to a data retention request (in some countries, a list of e.g. 16 users
> is OK), then AFAICS, you have to use IPFIX.
> 
> The implementation problem for this is compounded by the lack of state table
> on most BR implementations (e.g. how do you know when a UDP session has
> completed without state for that flow?)]
> 
> 
> "Confidentiality Warning: This message and any attachments are intended only
> for the use of the intended recipient(s).
> are confidential and may be privileged. If you are not the intended
> recipient. you are hereby notified that any
> review. re-transmission. conversion to hard copy. copying. circulation or
> other use of this message and any attachments is
> strictly prohibited. If you are not the intended recipient. please notify the
> sender immediately by return email.
> and delete this message and any attachments from your system.
> 
> Virus Warning: Although the company has taken reasonable precautions to
> ensure no viruses are present in this email.
> The company cannot accept responsibility for any loss or damage arising from
> the use of this email or attachment."
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires