## v6ops - Minutes Monday March 26th 0900 0900 meeting commences Agenda Bashing 6204bis dicussion is moved to thursday. draft-carpenter-v6ops-label-balance moves to moday Fred - iesg is asking about interim meeting to coincided with ripe meeting e.g. 24-28th of sept Question, how many will be a at ripe anyway? Answer, about a dozen hands. Low hum in favor. No opposition. First presentation - Experiences from IPv6-Only Networks with Transition Technologies in the WIDE Camp Spring 2012 http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-0.pdf mtu issues particularly with udp vpn applications many implmentation issues with nat64 and dns64 Fred B - Question, long term plans for the draft? Answer, and camp in sept updated version of the draft will follow. Second presentation - draft-donley-behave-deterministic-cgn-01 http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-1.pdf hinges on the question of address assignment efficiency due to fixed assignment of port resources. documented in draft that compression works fairly well between 10-100 users per ip. Fred B - Postponing question of whether would should take it until it ADs get back to us. test for donneley (done after following presentation) hum (mostly in favor) (minor opposition) Third presentation - NAT64 Operational Experience http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-2.ppt comments leading to updates of draft-chen-v6ops-nat64- experience-01 Moake chen - same question on the mtu statement Iljitsch B - so the ipv4 servers should set their mtu to at least 1260. good work item for v4 exit wg. Fred B - hold off or do it now? assuming there is no v4 exit is this a document suitable for this wg? hum (no support for) (or against) Fourth Presentation - 464XLAT Combination of Stateful and Stateless Translation http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-3.ppt Lorenzo C - like this as a hack to bring carrier pigeon quality v4 to v6 only devices. don't understand why the device needs a /96 (teathering) should should work with a /128 Fred B - history of draft ask softwire and behave chairs what they thought of it. right resolution to the narmative language is to split the document into the bcp for providing the service and another draft on the implementation report. seperate them. Lorenzo C - it's not a bcp right, you can do this using existing technology Philip M - service providers like standards. Janos M - I am very much against BCP Remi D - Support informational think coordination with softwire is required. Hui D - useful as short term before 3gpp rel 8 Question, does /96 requirement removal, remove objections to progress? Answer, 6 hands consider it a problem, 3 would not object after removal. Fifth Presentation - Stateless Source address mapping for ICMPv6 packets http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-5.ppt Fred B - we'll take it to WG last call on the mailing list. Sixth Presentation - IPv6 Guidance for Internet Content and Application Service Providers Lee H - it's a good doc Erik K - it's probably a good starting point. Hum for acceptance (some yes ) (no opposition) Fred B - repost as draft IETF Seventh Presentation - IPv6 Flow label for server load balancing http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-8.ppt Iljitsch B - it's dangerous to assume that the flow label is never going to change mid-session Lorenzo C - if the lb trusts the client to determine lb then you probably need to reset the label on ingress the draft should state that you don't trust the end host flow label. Erik K - having the policy says that you reserve the high bit for labels you set yourself could be worthwhile. Iljitsch B - I don't like this draft. Question, is it a indeterminate candidate for wg or not? Answer indeterminate hum in favor vs against. Session complete at 11:27 ## v6ops - Minutes Thursday March 29th 15:20 v6ops ietf 83 session 2 commenced at 15:20 First presentation - IP Transitioning in CE Routers draft-townsley-troan-ipv6-ce-transitioning (old slides) http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-4.pdf (new slides) http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-13.pptx Second presentation - RFC 6204 bis http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-11.pdf Ole T - DHCP fix going on in dhc WG Fred B - regarding M/O bits read all discussion and take it up in 3315bis Francis D - w 6/7 remove them. Question, ready for last call? Answer - hum, (some in favor) (no opposed) Question - no one prefers 6rd to native? Answer - native prefered Fred B - My perception is that we await an updated draft that deals with the issues highlighted and we can run through a last call and be ready to ship. Third presentation - Implementation Advice for RA-Guard http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-6.pdf Question, ready for wglc? Answer, hum (most in favor) (one opposed) Fourth presentation - Wireline: Incremental IPv6 http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-7.pptx Fred B - going to have at least one more draft revision. Question, hum for new version and after WGLC? Answer, (favored) (no opposed). Fifth presentation - SP Wi-Fi Services over Residential Architectures http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-12.pptx Philip M - does this belong in other standards bodies such as wfa or 3gpp (or bbf) Sixth Presentation - Using Only Link-Local Address In Network Core http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-9.pptx Janos M - wording is rather strong, prefer informational to bcp us of LL address is a matter of taste. Jan H - seems brilliant when you design it less so afterwards. Iljisch B - occasions where this is useful. Janos M - bgp needs global v6 addresses. Francois D - agree with iljisch meeting is concluded 1715