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

Let’s me be precise. This regulation must exist today. So there must exist a way to log the five-IPv4-tuple. If Ramesh combines the dhcpv6 logs with the current five-IPv4-tuple logs, will this be enough? From: "Rajiv Asati (rajiva)" Date: Tuesday, May 8, 2018 at 5:42 PM

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"

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

Thanks, Med. This makes it very explicit. -- Cheers, Rajiv From: "mohamed.boucad...@orange.com" Date: Monday, May 7, 2018 at 1:30 AM To: Rajiv Asati , Softwires-wg list , "int-a...@ietf.org" Cc:

Re: [Softwires] [dhcwg] WGLC for draft-ietf-dhc-dhcp4o6-saddr-opt - EXTENDED - Respond by April 17, 2018

Hi Ian: Thanks … suggested text changes look good. I would think it best to reference 3315bis … hopefully it won’t hold up publication of this draft since it may take RFC Editor a bit longer to process the 3315bis document, but they also will have a head start. (If it does hold it up and we

Re: [Softwires] [dhcwg] WGLC for draft-ietf-dhc-dhcp4o6-saddr-opt - EXTENDED - Respond by April 17, 2018

Hi Bernie, Many thanks for the review. I’ve had a look through your comments and they all look straightforward enough. They will be in the next version with Tomek’s comments. Here’s my suggestions in response to a couple of your comments: SECTION 9: - More of a question – do the