Re: [BEHAVE] Call for WG adoption of several documents

Hi,

We have set of explicit solution drafts out there, e.g. but not limited:
draft-korhonen-edns0-synthesis-flag-01
draft-savolainen-heuristic-nat64-discovery-00

The purpose of the draft-korhonen-behave-nat64-learn-analysis has been to compare various solutions and propose next steps.

In my opinion we might want to include content from draft-wing-behave-dns64-config to draft-korhonen-behave-nat64-learn-analysis, agree what is the best solution, write down the decision, and then also adopt some of the solutions.

It would be good to have the discussions now to progress before Prague.

My personal opinion, probably quite unsurprisingly, is that the "DNS Query for a Well-Known Name" (we will soon post update to draft-savolainen-heuristic-nat64-discovery that contains some updates learnt in discussions, like DNSSEC considerations) should be one and then additionally we might need an explicit solution as well (e.g. draft-korhonen-edns0-synthesis-flag). 

Best regards,

Teemu

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of ext Brian E Carpenter
> Sent: 14. helmikuuta 2011 22:29
> To: Dave Thaler
> Cc: 'behave' (behave@ietf.org)
> Subject: Re: [BEHAVE] Call for WG adoption of several documents
> 
> Hi,
> 
> On 2011-02-15 08:14, Dave Thaler wrote:
> > On our charter we have the following milestones for which there is no
> current WG document:
> > Apr 2011
> >
> > Submit to IESG: avoiding NAT64 with dual-stack host for local
> networks (std)
> >
> > Apr 2011
> >
> > Submit to IESG: NAT64 load balancing (std/info)
> >
> >
> > For the first milestone, the chairs believe there are two
> complementary drafts that together may meet the milestone.  These are:
> > draft-korhonen-behave-nat64-learn-analysis-
> 01<http://tools.ietf.org/html/draft-korhonen-behave-nat64-learn-
> analysis-01>
> > (-00 was presented last IETF, see minutes at
> http://www.ietf.org/proceedings/79/minutes/behave.txt)
> >
> >
> > http://tools.ietf.org/html/draft-wing-behave-dns64-config-02
> > (this was presented at IETF 77, see minutes at
> http://www.ietf.org/proceedings/77/minutes/behave.txt)
> 
> I don't think either of these drafts is quite there yet. They both
> discuss
> various solutions at some length, but neither of them is clearly
> proposing
> a single solution to the stated problem. draft-wing- does express a
> preference, but we haven't debated that.
> 
> Have we even debated whether the solution must work properly with
> untouched RFC3484-conforming hosts? I'd be very hesitant about any
> solution that *requires* host updates.
> 
> Also, I don't think either draft considers the case where a dual stack
> host receives a NAT64-based IPv6 address via an application layer
> referral,
> so that DNS is not part of the picture. Are we trying to solve that
> case too?
> 
> I think I'd rather see a new draft that contains only one solution. The
> existing
> drafts could then become informational background documents.
> 
> Don't we *also* need a solution to the main problem considered by
> draft-korhonen- (learn NAT64 prefix)? That isn't in the charter, but
> seems important.
> 
> > For the second milestone, there is:
> > http://tools.ietf.org/html/draft-zhang-behave-nat64-load-balancing-01
> > (-00 was presented last IETF, see minutes at
> http://www.ietf.org/proceedings/79/minutes/behave.txt)
> 
> If the goal is Informational, this draft is a good one to adopt.
> 
>    Brian
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave