![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
> > Do you mean as in RFC 3675? >>> >> I sometimes wonder how this RFC ever got off the ground. Its a bit of a joke. regards joe baptista -- Joe Baptista www.publicroot.org PublicRoot Consortium -------From ietf-bounces at ietf.org Fri Jun 27 20:29:47 2008 Return-Path: <ietf-bounces at ietf.org> X-Original-To: ietf-archive at megatron.ietf.org Delivered-To: ietfarch-ietf-archive at core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 13F473A6AB9; Fri, 27 Jun 2008 20:29:47 -0700 (PDT) X-Original-To: ietf at core3.amsl.com Delivered-To: ietf at core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDC213A6B00 for <ietf at core3.amsl.com>; Fri, 27 Jun 2008 20:29:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.976 X-Spam-Level: X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QximLB4ax87P for <ietf at core3.amsl.com>; Fri, 27 Jun 2008 20:29:44 -0700 (PDT) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by core3.amsl.com (Postfix) with ESMTP id A1AEF3A6A64 for <ietf at ietf.org>; Fri, 27 Jun 2008 20:29:44 -0700 (PDT) Received: by yw-out-2324.google.com with SMTP id 3so322349ywj.49 for <ietf at ietf.org>; Fri, 27 Jun 2008 20:29:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=wucBYlvwNVwLk1JUw04chD+KkBfJdZwvCb3CXr2UAek=; b=Yg4Ys34Pv2nKX2w9Ytt187g9Zq/Q/XNAbIgu026y5goLEaskzvqQgj4/ofxQLL4zhw 4M4hZKabAt9PNUYUSWnT7tw5SHZVlSvAfSrJqFzbR6stRnhTYnDvk7n6gAo8U5yLBpX4 zdoGPhUL9ojjvcRjzWhhc9RS+5PQr5Tnvj85Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=OX2NbAa1BjFIQyqLDeFoi5NZBkx69axAv2Ee57QkNPhAD7xZGHaNeGr0+If3k204Ab 5NKTCYm1u8Ng9JsC5YYx4negEO1G2yflfuA48ipW0FCYWjmoqDuQyw136pd54SAanz8F QquZdmEvuA688QZHjHiErRX8r+ZdIEn+gQd7Y= Received: by 10.150.219.3 with SMTP id r3mr3485814ybg.65.1214623788632; Fri, 27 Jun 2008 20:29:48 -0700 (PDT) Received: by 10.151.106.21 with HTTP; Fri, 27 Jun 2008 20:29:43 -0700 (PDT) Message-ID: <874c02a20806272029h38d3860cv816d27d5fecc553c at mail.gmail.com> Date: Fri, 27 Jun 2008 23:29:43 -0400 From: "Joe Baptista" <baptista at publicroot.org> To: "Joe Abley" <jabley at ca.afilias.info> Subject: Re: Update of RFC 2606 based on the recent ICANN changes ? In-Reply-To: <9486A1E5-864F-4B23-9EBA-697C1A7A7520 at ca.afilias.info> MIME-Version: 1.0 References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464 at multicasttech.com> <74E3E26A-FCFB-45C1-989A-DD7EA5752974 at virtualized.org> <6.2.5.6.2.20080627121824.02c55340 at resistor.net> <A9ACF7FB-BC78-44D9-AA61-4FCACE821677 at virtualized.org> <9486A1E5-864F-4B23-9EBA-697C1A7A7520 at ca.afilias.info> X-Google-Sender-Auth: 46e61185d67ba32e Cc: SM <sm at resistor.net>, ietf at ietf.org X-BeenThere: ietf at ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF-Discussion <ietf.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request at ietf.org?subject=unsubscribe> List-Post: <mailto:ietf at ietf.org> List-Help: <mailto:ietf-request at ietf.org?subject=help> List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request at ietf.org?subject=subscribe> Content-Type: multipart/mixed; boundary="===============0872126732==" Sender: ietf-bounces at ietf.org Errors-To: ietf-bounces at ietf.org
Do you mean as in RFC 3675?
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.