IETF Logo Mail Archive

Re: [sipcore] New Version Notification for draft-ibc-sipcore-sip-websocket-00 (previously draft-ibc-rtcweb-sip-websocket-00)

Iñaki Baz Castillo <ibc@aliax.net> Mon, 05 December 2011 13:37 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C43221F8BAA for <sipcore@ietfa.amsl.com>; Mon, 5 Dec 2011 05:37:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.527
X-Spam-Level:
X-Spam-Status: No, score=-2.527 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jCBLrSRT7-jk for <sipcore@ietfa.amsl.com>; Mon, 5 Dec 2011 05:37:52 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id D98E921F8B94 for <sipcore@ietf.org>; Mon, 5 Dec 2011 05:37:51 -0800 (PST)
Received: by vbbez10 with SMTP id ez10so1467471vbb.31 for <sipcore@ietf.org>; Mon, 05 Dec 2011 05:37:51 -0800 (PST)
Received: by 10.52.117.65 with SMTP id kc1mr4579933vdb.66.1323092271239; Mon, 05 Dec 2011 05:37:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.203.8 with HTTP; Mon, 5 Dec 2011 05:37:30 -0800 (PST)
In-Reply-To: <4EDCC858.8000607@digium.com>
References: <CALiegfm8Dv8kHE1xrt59vBzLzB29mOvjH6YR2m=vm=p_BtSBTw@mail.gmail.com> <CAGTXFp82jNsCUBM=j=Tq1Xc5cOr7P1Hbp9gv5MQyeVBoOS5=ng@mail.gmail.com> <5470070492D34F4EAC60E4ED91CB3841@gsmlaptop> <CALiegfmdxJQ+fAevUCfOaJjRkja-vW2Sqh-83-J=3_E5Ba1j6A@mail.gmail.com> <CA+cEqjc+2JR8S5i=kcpSz96KC_Mtd9OThafcGgeeAXaFEzZoWQ@mail.gmail.com> <CALiegfnCym7NdEs=TH=UtYjsK6jgqkVfHaeyHo1VU1QMTb-VyA@mail.gmail.com> <CA+cEqjctnA4_0Oef-juusN3=LUiao414DYUJhO6od+JYkutkJg@mail.gmail.com> <CALiegf=3HF3TdKof+Pghqzmzs192sDXRvO_GzU7TDODAT+bVwg@mail.gmail.com> <4EDCC858.8000607@digium.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 05 Dec 2011 14:37:30 +0100
Message-ID: <CALiegfmUMdJ7EFWaz61NBvNPdTxLqD90GL52iCqbx-TTvsChrQ@mail.gmail.com>
To: "Kevin P. Fleming" <kpfleming@digium.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: sipcore@ietf.org
Subject: Re: [sipcore] New Version Notification for draft-ibc-sipcore-sip-websocket-00 (previously draft-ibc-rtcweb-sip-websocket-00)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2011 13:37:52 -0000

2011/12/5 Kevin P. Fleming <kpfleming@digium.com>:
> "invalid.domain" is not a guaranteed-to-be-unassigned domain;
> "domain.invalid" is. There is an RFC defining such 'invalid' and 'example'
> domain names: RFC2606/BCP32.
>
> It would probably be best if your draft included the logic you've written
> above as the rationale for the use of a purposefully-invalid domain name,
> and then included a reference to RFC2606 so that readers will know why
> "domain.invalid" is in fact invalid.

Great, it will be added in a new revision.

Thanks a lot.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email