Re: [Softwires] [EXTERNAL] Re: ISP CGN logging inc. Destination ??
<Ramesh.R.Chandra@ril.com> Tue, 08 May 2018 05:16 UTC
Return-Path: <prvs=6595eda35=Ramesh.R.Chandra@ril.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 42C0312D959; Mon, 7 May 2018 22:16:05 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=Ramesh.R.Chandra@ril.com header.d=ril.com; dkim=pass (1024-bit key) header.d=ril.com
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 0RfEoCJLzb2c; Mon, 7 May 2018 22:16:02 -0700 (PDT)
Received: from GWJGSMTP014.ril.com (GWJGSMTP014.ril.com [116.50.64.21]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BAED12D883; Mon, 7 May 2018 22:15:57 -0700 (PDT)
DomainKey-Signature: s=ril; d=ril.com; c=nofws; q=dns; h=Authentication-Results:X-IronPort-AV:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader:Content-Type: MIME-Version:Content-Transfer-Encoding; b=VlPTo3B/j0OGxUHJ7ii60d7z5pQx3DdzXixnFVtSXpJIehQLncG3gPzX uGxRaJC63aqTpaUGdhSmu0e3R5GAejxWdwb6Tg+rpaQPgIuAW3wiaRtaP KSN8fXElFKXDobuBEtF1S10dANu5+QqvUoLRro+IxiA6uAKXDUYFj33qC E=;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ril.com; i=@ril.com; q=dns/txt; s=ril; t=1525756561; x=1557292561; h=from:to:cc:subject:thread-topic:thread-index:date: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: x-ms-exchange-transport-fromentityheader:content-type: mime-version:content-transfer-encoding: authentication-results:x-ironport-av; bh=twPT3oE8Zxh8dxfN7F1zzqPa4ICHd5CRz3CmeIBZqds=; b=mHf+XniwCJ5ZXSpOGsiRJQbfHOwlbVJw9qod4FjgEc4BXEUrKhSQdWn8 JeThE11MPVvtkZJx+Fs349smWSvhnD5dnqUzt/4nIZCPQmI/mdh4oKw7B vHJbwebk7Y2B3mrfKlCHN06mycKgJtA5Z4Cjr9M5y0/Fyg2IWrWPlzuve Y=;
Authentication-Results: GWJGSMTP014.ril.com; dkim=none (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="5.49,377,1520879400"; d="scan'208";a="17248251"
From: Ramesh.R.Chandra@ril.com
To: Yiu_Lee@comcast.com
CC: ianfarrer@gmx.com, rajiva@cisco.com, softwires@ietf.org, int-area@ietf.org
Thread-Topic: [EXTERNAL] Re: [Softwires] ISP CGN logging inc. Destination ??
Thread-Index: AQHT4yi6QsPwS4mEj0Wx5sa9RJtTQaQe3eyAgAAdZICAACCTAIAAfGTggAQuvoCAAYm2EA==
Date: Tue, 08 May 2018 05:15:48 +0000
Message-ID: <6b552bbdcc4146aa97386eb609c70e27@SHYDEXMBX08.in.ril.com>
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> <77D9057C-0310-4D03-BCA9-DBFC17CE9055@Cable.Comcast.com>
In-Reply-To: <77D9057C-0310-4D03-BCA9-DBFC17CE9055@Cable.Comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/wKCVF4vh864qwgmOIPjiE-1GgPg>
X-Mailman-Approved-At: Thu, 10 May 2018 03:32:36 -0700
Subject: Re: [Softwires] [EXTERNAL] Re: 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: Tue, 08 May 2018 05:16:05 -0000
Not really. Need IPv4 because desitination IP is on IPv4. Regds ramesh chandra M#: +91 90829 61303 O#: +91 22 7965 9762 -----Original Message----- From: Lee, Yiu [mailto:Yiu_Lee@comcast.com] Sent: 07 May 2018 16:46 To: Ramesh R Chandra Cc: ianfarrer@gmx.com; rajiva@cisco.com; softwires@ietf.org; int-area@ietf.org Subject: Re: [EXTERNAL] Re: [Softwires] ISP CGN logging inc. Destination ?? Just a quick thought. Will the dhcpv6 logs help? Sent from mobile device, pardon possible typo. > On May 7, 2018, at 7:06 AM, "Ramesh.R.Chandra@ril.com" <Ramesh.R.Chandra@ril.com> wrote: > > 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) > 2. Destination IP + Port (public) > 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 "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] ISP CGN logging inc. Destination ?? Rajiv Asati (rajiva)
- Re: [Softwires] [Int-area] ISP CGN logging inc. D… Dave O'Reilly
- Re: [Softwires] ISP CGN logging inc. Destination … ianfarrer
- Re: [Softwires] ISP CGN logging inc. Destination … Rajiv Asati (rajiva)
- Re: [Softwires] [Int-area] ISP CGN logging inc. D… Rajiv Asati (rajiva)
- Re: [Softwires] [Int-area] ISP CGN logging inc. D… Dave O'Reilly
- Re: [Softwires] ISP CGN logging inc. Destination … ianfarrer
- Re: [Softwires] ISP CGN logging inc. Destination … mohamed.boucadair
- Re: [Softwires] ISP CGN logging inc. Destination … Ramesh.R.Chandra
- Re: [Softwires] [EXTERNAL] Re: ISP CGN logging in… Lee, Yiu
- Re: [Softwires] ISP CGN logging inc. Destination … mohamed.boucadair
- Re: [Softwires] ISP CGN logging inc. Destination … mohamed.boucadair
- Re: [Softwires] [EXTERNAL] RE: Re: ISP CGN loggin… Lee, Yiu
- Re: [Softwires] ISP CGN logging inc. Destination … Rajiv Asati (rajiva)
- Re: [Softwires] [EXTERNAL] Re: ISP CGN logging in… Rajiv Asati (rajiva)
- Re: [Softwires] [EXTERNAL] Re: ISP CGN logging in… Lee, Yiu
- Re: [Softwires] ISP CGN logging inc. Destination … mohamed.boucadair
- Re: [Softwires] ISP CGN logging inc. Destination … Rajiv Asati (rajiva)
- Re: [Softwires] [EXTERNAL] Re: ISP CGN logging in… Ramesh.R.Chandra
- Re: [Softwires] [EXTERNAL] Re: ISP CGN logging in… Ramesh.R.Chandra
- Re: [Softwires] ISP CGN logging inc. Destination … Rajiv Asati (rajiva)
- Re: [Softwires] ISP CGN logging inc. Destination … Gottlieb, Jordan J
- Re: [Softwires] ISP CGN logging inc. Destination … ianfarrer
- Re: [Softwires] ISP CGN logging inc. Destination … Gottlieb, Jordan J