Hi Med, I share the same concern. While such a requirement may be deemed reasonable, it does not warrant nullifying the very advantage stateless 4o6 techniques such as MAP bring to bear.
If such a requirement carries over to native IPv6 communication (involving no address translation), then it would warrant a solution such as IPFIX anyway, in which case, it would also implicitly solve for the stateless 4o6 techniques. -- Cheers, Rajiv From: "mohamed.boucad...@orange.com" <mohamed.boucad...@orange.com> Date: Wednesday, May 9, 2018 at 3:30 AM To: Rajiv Asati <raj...@cisco.com>, "ramesh.r.chan...@ril.com" <ramesh.r.chan...@ril.com>, "yiu_...@comcast.com" <yiu_...@comcast.com> Cc: Softwires-wg list <softwires@ietf.org>, "int-a...@ietf.org" <int-a...@ietf.org> Subject: RE: [Softwires] Re: ISP CGN logging inc. Destination ?? Hi Rajiv, What concerns me with this requirement is that it nullifies one of the motivations for stateless address sharing: https://tools.ietf.org/html/draft-ietf-softwire-stateless-4v6-motivation-05#section-3.1.3 (Logging - No Need for Dynamic Binding Notifications) especially, this part: Some Service Providers have a requirement to use only existing logging systems and to avoid introducing new ones (mainly because of Capital Expenditure (CAPEX) considerations). This requirement is easily met with stateless solutions. Cheers, Med De : Softwires [mailto:softwires-boun...@ietf.org] De la part de Rajiv Asati (rajiva) Envoyé : mardi 8 mai 2018 23:43 À : ramesh.r.chan...@ril.com; yiu_...@comcast.com Cc : softwires@ietf.org; int-a...@ietf.org Objet : Re: [Softwires] [EXTERNAL] Re: ISP CGN logging inc. Destination ?? Agree with Ramesh. DHCP(v6) helps with logging source IP assignment, but that’s it. The requirement here is about keeping track of not only source IP+port, but also destination IP+port per connection. DHCP(v6) doesn’t apply here. -- Cheers, Rajiv From: "ramesh.r.chan...@ril.com<mailto:ramesh.r.chan...@ril.com>" <ramesh.r.chan...@ril.com<mailto:ramesh.r.chan...@ril.com>> Date: Tuesday, May 8, 2018 at 1:15 AM To: "yiu_...@comcast.com<mailto:yiu_...@comcast.com>" <yiu_...@comcast.com<mailto:yiu_...@comcast.com>> Cc: "ianfar...@gmx.com<mailto:ianfar...@gmx.com>" <ianfar...@gmx.com<mailto:ianfar...@gmx.com>>, Rajiv Asati <raj...@cisco.com<mailto:raj...@cisco.com>>, Softwires-wg list <softwires@ietf.org<mailto:softwires@ietf.org>>, "int-a...@ietf.org<mailto:int-a...@ietf.org>" <int-a...@ietf.org<mailto:int-a...@ietf.org>> Subject: RE: [EXTERNAL] Re: [Softwires] ISP CGN logging inc. Destination ?? 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_...@comcast.com] Sent: 07 May 2018 16:46 To: Ramesh R Chandra Cc: ianfar...@gmx.com<mailto:ianfar...@gmx.com>; raj...@cisco.com<mailto:raj...@cisco.com>; softwires@ietf.org<mailto:softwires@ietf.org>; int-a...@ietf.org<mailto:int-a...@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.chan...@ril.com<mailto:ramesh.r.chan...@ril.com>" <ramesh.r.chan...@ril.com<mailto:ramesh.r.chan...@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: ianfar...@gmx.com<mailto:ianfar...@gmx.com> [mailto:ianfar...@gmx.com] Sent: 04 May 2018 17:28 To: Rajiv Asati (rajiva) Cc: Softwires-wg list; int-a...@ietf.org<mailto:int-a...@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) <raj...@cisco.com<mailto:raj...@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<mailto: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 mailing list Softwires@ietf.org https://www.ietf.org/mailman/listinfo/softwires
