Hallo IPv6-Freunde, sorry for dups - aber das sind doch recht interessante Dinge. Ich bin nicht mit im Team, aber ich kann sicher Meinungen/Wünsche etc. einbringen. Gruss, Juergen Rauschenbach >From: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], > [EMAIL PROTECTED], [EMAIL PROTECTED] >Subject: UPDATE on DNS / DHCPv6 RFQ >Date: Wed, 28 Mar 2001 11:30:16 -0600 >X-Mailer: Internet Mail Service (5.5.2652.78) >Sender: [EMAIL PROTECTED] > >Members, > >I am so proud of you all and all the members. I am getting very good >commitments from our community to build an awesome and powerful team for >this RFQ for DNS + DHCPv6. But also mail where some are getting confused. >Let me try to set all at ease and present a picture of what will happen here >and the plan. First the plan will evolve as we get it started as I did to >gather vendors to support the BIND 9 vendor consortia who gave us all BIND >working with the Internet Software Consortia (ISC) and non-profit company >that provides bind DNS by contracting programmers to do the work. > >Also I have taken the liberty to cc Paul Vixie and David Conrad who lead the >processes for BIND 9. They will both be part of this team. Also Ralph Droms >from Cisco who will also be part of this team and IETF DHC Chair and >co-author of DHCPv6. Ralph has offered to be on the team and help too. > >Let me do this like a Q&A session: > >Q: What is an RFQ what is the objective?: > >An RFQ is Request for Quote as opposed to Request for Comment (RFC not to be >confused with IETF notion of RFC and why I am using RFQ to avoid people >getting paranoid we are doing IETF work). An RFQ puts out the technical >requirements and laundry list of what is required and opens the bidding >process to get the work started. Once a bidder is selected more details are >defined and final cost is agreed to. So step 1 is the RFQ. It gives all an >idea of what is to be done and what the cost will be. And who could do the >work. > >Q. What will the team do and why not have a DNS and DHCPv6 Team? > >The team (being built now) will discuss and define the technical >requirements and implementation requirements for next version of BIND DNS >and a new code base for DHCPv6. Both of these MUST be done with an "open >source" mindset. The team will first work on DNS and then on DHCPv6. DNS >will be more difficult as we have existing code base and compatibility >issues with previous releases. We also MUST get DNS to support native IPv6 >transport and APIs A.S.A.P. and the "PRIORITY" of this work. But the team >will also look at DNS issues we see today in BIND 9 like the performace of >BIND 9 is not where we all would like it to be and APIs exposed should be >able to target security actions. I will not split this into two teams >unless that is absolutely required and it is not at least initially. Many >people responding have expertise for both DNS and DHCPv6. > >Q. Why only 2 people from anyone Member entity? > >This just has to be because we have to make sure that its a fair process and >any exceptions have to be seriously justified and really explained. One >example would be if someone was consulting or driving the process. For >example if we want Erik Nordmark as consultant to the process from Sun that >would not count towards Sun's 2 people. Also I will be very busy leading >this and having two people from Nokia besides me would be fair. > >Do you want me to make this 3 people from each entity? I can see why we >should? > >Q. Non-Members on the Team? > >This will include leaders and engineers associated with Nominum and ISC who >have built the Open Source for BIND and DHCPv4. We want to have these >people to help us and be availble to answer questions for the team. Also >University and Research Institutes who have contributed greatly to the >process or code base for the DNS open source community. > >Q. What do we do about selecting the entity and future issues and divergent >code base? > >Let me just cut to the chase and be direct. There are two concerns here. > >1. What if the vendor we pick gets bought out and then charges excessive >license fees for the software we put in the Open Source pool of planet >earth. Well this is why my bias will be that ISC bids on this and if others >bid as a company we will develop a contract so that the source is moved >under those circumstances to another Open Source supplier. Or we move it >ourselves. There are many methods to avoid this problem if you plan for it >up front. I will not let the Forum or vendors on this list get burned by >evil and abusive business practices. Don't worry this will be handled trust >me. I am death on those who have such business practices as they give >enlightened capitalism a bad name. > >2. Divergent code base is not a problem for DHCPv6. We will require that >this code base be compatible if possible with BIND DNS as thats what most of >us are using at this time. But, I do think we need to be open to having the >most robust and performing DNS implementation for IPv6. If ISC is to >continue to exist and provide BIND then we really must work to avoid >divergent code base down the road. This will be a key discussion point for >the entire team. > >Q. What about DNS and DHCPv6 security? > >The team will discuss this in depth and hear all ideas > >Q. Whats the Technical Directorates role? > >Key members of the Technical Directorate will be on the Team who have the >DNS and DHCPv6 knowledge. And essentially this was spawned by the >Technical Directorate. > >Q. Whats a thumb nail sketch of the process? > >RIght now here is a sketch of the plan which will evolve. > >Steps: >1. Team is built and mail list is set up (2 weeks) >2. Team defines reqs and process and list (8 weeks) >3. Team delivers proposal to the IPv6 Forum Board for Review (1 week) >4. Team delivers proposal to the Members (this list and for 1 week) >5. IPv6 Forum Board and others as required draft the RFQ and statements (1 >week as they should be working on this in Step 3). >6. Send out RFQ to the market later part of July 2001 >7. Set up meeting with what we have to meet at London IETF 1st week of >August for face to face. > >Now we have a bunch of admin stuff to do to get the lists and team >coordinated and go do the work. > >If we slip on the time frames I will report that to you Members. > >thanks >/jim >Chair IPv6 Forum Technical Directorate ####* ##### ## ## DFN-Verein Dr. Juergen Rauschenbach ## #* ## ### ## Anhalter Str. 1 Phone : +49 30 884299 46 ## ## #### ###### D-10963 Berlin Fax : +49 30 884299 70 ## #* ## ## ### Germany E-Mail: [EMAIL PROTECTED] ####* ## ## ## http://www.dfn.de [EMAIL PROTECTED]
