
From morgaine.dinova@googlemail.com  Sun May  2 11:47:41 2010
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAE0D3A6AC5 for <vwrap@core3.amsl.com>; Sun,  2 May 2010 11:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.088
X-Spam-Level: **
X-Spam-Status: No, score=2.088 tagged_above=-999 required=5 tests=[AWL=-2.035,  BAYES_99=3.5, 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 SSe5sbgp8Mdv for <vwrap@core3.amsl.com>; Sun,  2 May 2010 11:47:39 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 7B3283A6A00 for <vwrap@ietf.org>; Sun,  2 May 2010 11:47:36 -0700 (PDT)
Received: by wwb24 with SMTP id 24so1338517wwb.31 for <vwrap@ietf.org>; Sun, 02 May 2010 11:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=ae6UUoux+IUsTuy26nsegxpGBte+n1dysJY/7/a5D0o=; b=VLMHBFKHMPhmLFhiAVnh2nSKlbZpS6iQbFyswwZhLaDBIPw2a6OFj3NMAwMh5R9rgj S/SCCZaQZJ546BBgSh8lmru/PVZdjuAEbrVINpUPfrP/mz6pkZOwXb8TSfqyjFnCjnfr qTvR42tx/WUm7rI8ZBKEQoMFKPEeigsLS4Ing=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=eBUNiewVrRzkUWHeDowI+SW7IOcPLURKesiIWkGbik/X4BdadcjTYyVs53kC7/UQcm wqCKQLbUvnqRPzNprpE/hPusDB3YSpO8O0FC112q9zfnosSMp+JBsQdJGlbRjCgE7fSx tcLvNFw/tPoPSSF4pUJPScRr6sL7tHu3DDxuo=
MIME-Version: 1.0
Received: by 10.216.86.129 with SMTP id w1mr6806121wee.174.1272826037618; Sun,  02 May 2010 11:47:17 -0700 (PDT)
Received: by 10.216.25.6 with HTTP; Sun, 2 May 2010 11:47:17 -0700 (PDT)
Date: Sun, 2 May 2010 19:47:17 +0100
Message-ID: <k2ke0b04bba1005021147p673b9eafhce753e4ce921ab3d@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d78545d5480c0485a0e76e
Subject: [vwrap] New progress in VW group IM interop: Jarilo
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 May 2010 18:47:42 -0000

--0016e6d78545d5480c0485a0e76e
Content-Type: text/plain; charset=ISO-8859-1

Over the last few days, *chat interoperability* between VWs has taken a
significant step forward.

Our AWG friend Latif Khalifa (who also develops the Radegast 2D client and
is part of the libomv team) has created a practical chat bridge between VWs
and classic IM systems, called Jarilo <http://code.google.com/p/jarilo/>,
developed as an open source project.  This currently interoperates Second
Life and/or Opensim group chat and IRC and XMPP conferencing systems, and in
principle could be extended with other IM protocol modules.

Any number and combination of VW chat groups, IRC channels and Jabber rooms
could be bridged in this way.  These individual chat services are
topologically similar in the sense that each defines a flat or single-level
logical grouping of participants, even when implemented across multiple
linked servers.  Jarilo bridges these individual, internally cohesive groups
to form a *metagroup* that does not have the same uniformity, but instead
reflects the diversity of its component subgroups.  Two or more such
metagroups could of course themselves be bridged to create a hierarchical
architecture if desired.

Currently we are experimenting only with triples of component services, each
triple consisting of one SL chat group, one IRC channel and one Jabber
room.  (This is just a choice, not a restriction in the software.)  Two such
triples are currently being tested:


   - The SL group *AW Groupies* (the community arm of the Architecture
   Working Group in SL that was created for interop), the IRC channel *#awg*on
   irc.freenode.net, and the XMPP room *awg* at conference.jabber.org.


   - The SL group *VWRAP Chat*, the IRC channel *#vwrap* on irc.freenode.net,
   and the XMPP room *vwrap* at conference.jabber.org.  *[IMPORTANT:  these
   are informal chat groups and the IETF "Note Well" does not apply in any of
   them nor in the metagroup, despite their VWRAP-related names.]*



(Note that the Opensim-based OSgrid group chat is not currently part of
these tests only because it is non-functional after recent infrastructure
changes.  This is likely to be remedied in short order.)

Because it is an external service, it is easy to see Jarilo as leading
towards the kind of decoupled services that VWRAP will be gluing together
into VW deployments.  It is very noteworthy that this provides chat interop
through client-based interfacing, without requiring interoperable chat
services to be planned and provided by world providers.  This independence
is a very empowering property for VW users, and highlights the point that
David made some months ago about services becoming independent seats of
policy.

Althought Jarilo has only just come into operation and is still at an early
stage of development, it is already providing very valuable practical
experience about both the benefits and the problems of IM interop among
virtual worlds and conferencing systems.

It is important to note that two of the VWs in current use by AWG members
(OpenWonderland and OpenCobalt) employ XMPP for their chat systems, and
hence Jarilo represents real interop of one very important component in
current use by at least 4 different VW implementations.  (Tests between
actual VWs are expected soon.)


Morgaine.

--0016e6d78545d5480c0485a0e76e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Over the last few days, <b>chat interoperability</b> between VWs has taken =
a significant step forward.<br><br>Our AWG friend Latif Khalifa (who also d=
evelops the Radegast 2D client and is part of the libomv team) has created =
a practical chat bridge between VWs and classic IM systems, called <a href=
=3D"http://code.google.com/p/jarilo/" target=3D"_blank">Jarilo</a>, develop=
ed as an open source project.=A0 This currently interoperates Second Life a=
nd/or Opensim group chat and IRC and XMPP conferencing systems, and in prin=
ciple could be extended with other IM protocol modules.<br>

<br>Any number and combination of VW chat groups, IRC channels and Jabber r=
ooms could be bridged in this way.=A0 These individual chat services are to=
pologically similar in the sense that each defines a flat or single-level l=
ogical grouping of participants, even when implemented across multiple link=
ed servers.=A0 Jarilo bridges these individual, internally cohesive groups =
to form a <i><b>metagroup</b></i> that does not have the same uniformity, b=
ut instead reflects the diversity of its component subgroups.=A0 Two or mor=
e such metagroups could of course themselves be bridged to create a hierarc=
hical architecture if desired.<br>

<br>Currently we are experimenting only with triples of component services,=
 each triple consisting of one SL chat group, one IRC channel and one Jabbe=
r room.=A0 (This is just a choice, not a restriction in the software.)=A0 T=
wo such triples are currently being tested:<br>
<br><ul><li>The SL group <b>AW Groupies</b> (the community arm of the Archi=
tecture Working Group in SL that was created for interop), the IRC channel =
<b>#awg</b> on <a href=3D"http://irc.freenode.net">irc.freenode.net</a>, an=
d the XMPP room <b>awg</b> at <a href=3D"http://conference.jabber.org">conf=
erence.jabber.org</a>.</li>

</ul><ul><li>The SL group <b>VWRAP Chat</b>, the IRC channel <b>#vwrap</b> =
on <a href=3D"http://irc.freenode.net">irc.freenode.net</a>, and the XMPP r=
oom <b>vwrap</b> at <a href=3D"http://conference.jabber.org">conference.jab=
ber.org</a>.=A0 <i>[IMPORTANT:=A0 these are informal chat groups and the IE=
TF &quot;Note Well&quot; does not apply in any of them nor in the metagroup=
, despite their VWRAP-related names.]</i><br>

</li></ul><br><br>(Note that the Opensim-based OSgrid group chat is not cur=
rently part of these tests only because it is non-functional after recent i=
nfrastructure changes.=A0 This is likely to be remedied in short order.)<br=
>

<br>Because it is an external service, it is easy to see Jarilo as leading =
towards the kind of decoupled services that VWRAP will be gluing together i=
nto VW deployments.=A0 It is very noteworthy that this provides chat intero=
p through client-based interfacing, without requiring interoperable chat se=
rvices to be planned and provided by world providers.=A0 This independence =
is a very empowering property for VW users, and highlights the point that D=
avid made some months ago about services becoming independent seats of poli=
cy.<br>

<br>Althought Jarilo has only just come into operation and is still at an e=
arly stage of development, it is already providing very valuable practical =
experience about both the benefits and the problems of IM interop among vir=
tual worlds and conferencing systems.<br>

<br>It is important to note that two of the VWs in current use by AWG membe=
rs (OpenWonderland and OpenCobalt) employ XMPP for their chat systems, and =
hence Jarilo represents real interop of one very important component in cur=
rent use by at least 4 different VW implementations.=A0 (Tests between actu=
al VWs are expected soon.)<br>

<br><br>Morgaine.<br><br><br>

--0016e6d78545d5480c0485a0e76e--

From suzyque@gmail.com  Mon May  3 06:21:15 2010
Return-Path: <suzyque@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A24F28C1DB for <vwrap@core3.amsl.com>; Mon,  3 May 2010 06:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.223
X-Spam-Level: ***
X-Spam-Status: No, score=3.223 tagged_above=-999 required=5 tests=[BAYES_80=2,  FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_47=0.6]
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 ItiSZMRP7+Hw for <vwrap@core3.amsl.com>; Mon,  3 May 2010 06:21:12 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 105973A6CBF for <vwrap@ietf.org>; Mon,  3 May 2010 06:19:27 -0700 (PDT)
Received: by fxm4 with SMTP id 4so2328474fxm.31 for <vwrap@ietf.org>; Mon, 03 May 2010 06:19:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:reply-to:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=LQk4dtv6NV02akduj7GgdDakzrVfQ8EWhm3Ymey7Ml4=; b=FAVYj+IOZmqW2w7v3xiznnOzOH35kB9qIybS4fAiDHKZlE94vj3EAe0SDMosAVfqnd Fvwc4pdvLlEhO3rrzM+0u0VKG31BtDXpGmNOXRSgHER3MJWHkkgGnQvqJLSeaZli8svQ iG3wLTSDz1AgBKk85PsFzEXUrIxya9Ssvoq/w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=crS98fVJXWNQ3D0IZpSepepGo9gD+bvxwdeRlGMDmqF2lpAs5QV4udeEQX8fC9hqvN p1NFTqblHmBOeZp6zgjOxn+vtOL2hN7EL2WaHv/jnl+6SSAxmQjdW13GawPMWf4MJ+4M RoytNDu2vJV3JO2xd50PgmCXLSbr+83ehydKo=
MIME-Version: 1.0
Received: by 10.223.24.148 with SMTP id v20mr3336356fab.43.1272892750674; Mon,  03 May 2010 06:19:10 -0700 (PDT)
Sender: suzyque@gmail.com
Received: by 10.223.104.132 with HTTP; Mon, 3 May 2010 06:19:10 -0700 (PDT)
In-Reply-To: <4BD8D9F3.9000709@intel.com>
References: <OF12BB21F8.3FAB95C0-ON85257712.0076D115-85257712.00773210@us.ibm.com> <t2vb325928b1004281737qfbde4969vc296d331cf5d3eef@mail.gmail.com> <4BD8D9F3.9000709@intel.com>
Date: Mon, 3 May 2010 08:19:10 -0500
X-Google-Sender-Auth: 579435a93bb72fea
Message-ID: <t2h2bd5b7f11005030619g604e3909i9cc3cfe8c97cd02b@mail.gmail.com>
From: Suzy Deffeyes <suzyq@pobox.com>
To: John Hurliman <john.hurliman@intel.com>
Content-Type: multipart/alternative; boundary=001517447b5a3db9ee0485b070e4
Cc: vwrap@ietf.org
Subject: Re: [vwrap] Some thoughts on Josh's Linden Lab Legacy Protocol discussion
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: suzyq@pobox.com
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 May 2010 13:21:15 -0000

--001517447b5a3db9ee0485b070e4
Content-Type: text/plain; charset=ISO-8859-1

This begins to sound a bit like the OpenGL extension process. OpenGL's
process is a bit of overkill for our needs, but something similar might be
useful to us.

In OpenGL, a vendor can create a proprietary extension. It is named for the
vendor, so that potential users (ISVs) know it will probably not work on
other hardware.  If the vendor chooses to do so, the spec for that
proprietary extension can be made public. Occasionally two vendors will
cooperate on a spec,usually outside the OpenGL standards process, and can
put out a joint spec labeled EXT. When the OpenGL ARB (Architecture Review
Board) is ready to move an extension closer to being in the core, an ARB
labeled spec can be created, at this point the spec gets discussed,
designed, and voted on by the ARB. It is normal for widely implemented ARB
specs to eventually get rolled into core, at which point they are required
to be implemented by all vendors supporting that level of OpenGL.

>From a standards point of view, it helps weed out the features that aren't
widely implemented, and gives a spec time to evolve before it becomes part
of the required core.  Vendors can choose if there is value in trying to get
the extension widely used (by pushing it down the EXT/ARB path), or they can
choose to have it be super s3cr3t.  There is a naming convention that
indicates how widely available an extension is, and OpenGL licensees each
get their own block of enumerants so that extensions don't stomp on each
other.

>From an ISV standpoint, it's a little difficult to manage. An ISV might
implement their code using the EXT extension, and then not move to the ARB
or core versions of the functionality. That means that vendors end up
dragging around support for a lot of different extensions.

And FYI, in the COLLADA group we are also currently considering a more
formal extension mechanism as well.

Suzy Deffeyes/Pixel Gausman
IBM

On Wed, Apr 28, 2010 at 7:59 PM, John Hurliman <john.hurliman@intel.com>wrote:

> +1 to moving forward with a bare minimum set of requirements. The trap I
> want to avoid is getting rough consensus that there are a ten different
> areas where we need to standardize communication, but when it comes time to
> actually doing the standards work it turns out only five of those areas are
> relevant to the active participants. The other five areas receive a fair
> dose of idle speculation, but otherwise go nowhere and stall the overall
> process.
>
> If anyone identifies a specific resource (service endpoint, set of
> endpoints, suite of bi-directional events, whatever) that they want to see
> standardized, I would prefer to see it drafted / prototyped / alpha tested
> before arguing that it should be officially sanctioned by VWRAP.
>
> John
>
>

--001517447b5a3db9ee0485b070e4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

This begins to sound a bit like the OpenGL extension process. OpenGL&#39;s =
process is a bit of overkill for our needs, but something similar might be =
useful to us. <br><br>In OpenGL, a vendor can create a proprietary extensio=
n. It is named for the vendor, so that potential users (ISVs) know it will =
probably not work on other hardware.=A0 If the vendor chooses to do so, the=
 spec for that proprietary extension can be made public. Occasionally two v=
endors will cooperate on a spec,usually outside the OpenGL standards proces=
s, and can put out a joint spec labeled EXT. When the OpenGL ARB (Architect=
ure Review Board) is ready to move an extension closer to being in the core=
, an ARB labeled spec can be created, at this point the spec gets discussed=
, designed, and voted on by the ARB. It is normal for widely implemented AR=
B specs to eventually get rolled into core, at which point they are require=
d to be implemented by all vendors supporting that level of OpenGL. <br>
<br>From a standards point of view, it helps weed out the features that are=
n&#39;t widely implemented, and gives a spec time to evolve before it becom=
es part of the required core.=A0 Vendors can choose if there is value in tr=
ying to get the extension widely used (by pushing it down the EXT/ARB path)=
, or they can choose to have it be super s3cr3t.=A0 There is a naming conve=
ntion that indicates how widely available an extension is, and OpenGL licen=
sees each get their own block of enumerants so that extensions don&#39;t st=
omp on each other. <br>
<br>From an ISV standpoint, it&#39;s a little difficult to manage. An ISV m=
ight implement their code using the EXT extension, and then not move to the=
 ARB or core versions of the functionality. That means that vendors end up =
dragging around support for a lot of different extensions. <br>
<br>And FYI, in the COLLADA group we are also currently considering a more =
formal extension mechanism as well. <br><br>Suzy Deffeyes/Pixel Gausman<br>=
IBM<br><br><div class=3D"gmail_quote">On Wed, Apr 28, 2010 at 7:59 PM, John=
 Hurliman <span dir=3D"ltr">&lt;<a href=3D"mailto:john.hurliman@intel.com">=
john.hurliman@intel.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">+1 to moving forw=
ard with a bare minimum set of requirements. The trap I want to avoid is ge=
tting rough consensus that there are a ten different areas where we need to=
 standardize communication, but when it comes time to actually doing the st=
andards work it turns out only five of those areas are relevant to the acti=
ve participants. The other five areas receive a fair dose of idle speculati=
on, but otherwise go nowhere and stall the overall process.<br>

<br>
If anyone identifies a specific resource (service endpoint, set of endpoint=
s, suite of bi-directional events, whatever) that they want to see standard=
ized, I would prefer to see it drafted / prototyped / alpha tested before a=
rguing that it should be officially sanctioned by VWRAP.<br>

<br>
John<div><div></div><br></div></blockquote></div><br>

--001517447b5a3db9ee0485b070e4--

From john.hurliman@intel.com  Thu May  6 10:37:10 2010
Return-Path: <john.hurliman@intel.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB38C3A6A16 for <vwrap@core3.amsl.com>; Thu,  6 May 2010 10:37:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.566
X-Spam-Level: 
X-Spam-Status: No, score=-4.566 tagged_above=-999 required=5 tests=[AWL=-0.567, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
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 R6w-NLaNd4ot for <vwrap@core3.amsl.com>; Thu,  6 May 2010 10:37:09 -0700 (PDT)
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by core3.amsl.com (Postfix) with ESMTP id C6DD63A695F for <vwrap@ietf.org>; Thu,  6 May 2010 10:37:09 -0700 (PDT)
Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 06 May 2010 10:35:31 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.52,342,1270450800"; d="scan'208";a="619491576"
Received: from rrsmsx604.amr.corp.intel.com ([10.31.0.170]) by orsmga001.jf.intel.com with ESMTP; 06 May 2010 10:36:43 -0700
Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx604.amr.corp.intel.com ([10.31.0.170]) with mapi; Thu, 6 May 2010 11:36:52 -0600
From: "Hurliman, John" <john.hurliman@intel.com>
To: "vwrap@ietf.org" <vwrap@ietf.org>
Date: Thu, 6 May 2010 11:36:50 -0600
Thread-Topic: ECMA-262 and the Real LLSD type
Thread-Index: AcrtQVFTMTAh+WZoRxODmnWWCjSDjA==
Message-ID: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [vwrap] ECMA-262 and the Real LLSD type
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 17:37:10 -0000

In draft-hamrick-llsd-00 "3.2. JSON Serialization" it states:

   Real  LLSD 'Real' values are represented by the JSON non-terminal 'numbe=
r'.

Then later in "Appendix A. ABNF of Real Values" it lists a series of string=
s that can be converted into real values:

   negative-infinity =3D  %x2D.49.6E.66.69,6E.69.74.79   ; "-Infinity"
   negative-zero     =3D  %x2D.5A.65.72.6F               ; "-Zero"
   zero              =3D  %x30.2E.30                     ; "0.0"
   positive-zero     =3D  %x2B.5A.65.72.6F               ; "+Zero"
   positive-infinity =3D  %x2B.49.6E.66.69,6E.69.74.79   ; "+Infinity"
   signaling-nan       =3D  %4E.61.4E.53                   ; "NaNS"
   quiet-nan         =3D  %4E.61.4E.51                   ; "NaNQ"

Does this mean that an LLSD real type with a value of -Infinity needs to be=
 converted to a JSON string, and would be decoded on the receiving side as =
an LLSD string with value "-Infinity" (that happens to have a valid convers=
ion to an LLSD real)? ECMA-262 does not support Infinity, NaN, etc. for the=
 JSON 'number' type so it looks like we need to transmit those values as st=
rings.

John

From josh@lindenlab.com  Thu May  6 11:48:06 2010
Return-Path: <josh@lindenlab.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4DBD3A69F6 for <vwrap@core3.amsl.com>; Thu,  6 May 2010 11:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.924
X-Spam-Level: 
X-Spam-Status: No, score=0.924 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6]
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 3gNQD+kTTF2a for <vwrap@core3.amsl.com>; Thu,  6 May 2010 11:48:06 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id F09883A68A0 for <vwrap@ietf.org>; Thu,  6 May 2010 11:48:05 -0700 (PDT)
Received: by vws9 with SMTP id 9so286660vws.31 for <vwrap@ietf.org>; Thu, 06 May 2010 11:47:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.108.227 with SMTP id g35mr1835236vcp.184.1273171670130;  Thu, 06 May 2010 11:47:50 -0700 (PDT)
Received: by 10.220.73.13 with HTTP; Thu, 6 May 2010 11:47:49 -0700 (PDT)
In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com>
References: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com>
Date: Thu, 6 May 2010 11:47:49 -0700
Message-ID: <v2jf72742de1005061147qad927bb3p9c268fc18b1d0995@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: "vwrap@ietf.org" <vwrap@ietf.org>
Content-Type: multipart/alternative; boundary=00c09f8de5392393690485f1615e
Subject: Re: [vwrap] ECMA-262 and the Real LLSD type
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 18:48:07 -0000

--00c09f8de5392393690485f1615e
Content-Type: text/plain; charset=UTF-8

("from the floor")

On Thu, May 6, 2010 at 10:36 AM, Hurliman, John <john.hurliman@intel.com>wrote:

> In draft-hamrick-llsd-00 "3.2. JSON Serialization" it states:
>
> (snip)


> Does this mean that an LLSD real type with a value of -Infinity needs to be
> converted to a JSON string, and would be decoded on the receiving side as an
> LLSD string with value "-Infinity" (that happens to have a valid conversion
> to an LLSD real)? ECMA-262 does not support Infinity, NaN, etc. for the JSON
> 'number' type so it looks like we need to transmit those values as strings.
>

That looks like a reasonable interpretation/suggestion to me.

While we're nitpicking this part of the spec:

* The ABNF for non-special real numbers is pretty b0rked if I'm reading it
correctly. (The exponent is non-optional, negative numbers are not
productions, '0.00' is forbidden, etc) I've mentioned this to Mark Lentczner
off-list.

* are '+Zero' and '-Zero' really preferable over '0.0' and '-0.0' ? Who uses
them?

* should 'Infinity' (sans-+) be considered valid? how about 'NaN' (no 'S' or
'Q')?

* was this all just a conspiracy by the draft authors to get us talking
about their alter egos?

--00c09f8de5392393690485f1615e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>(&quot;from the floor&quot;)</div><div><br></div><div>On Thu, May 6, 2=
010 at 10:36 AM, Hurliman, John <span dir=3D"ltr">&lt;<a href=3D"mailto:joh=
n.hurliman@intel.com">john.hurliman@intel.com</a>&gt;</span> wrote:</div><d=
iv>
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">In draft-hamrick=
-llsd-00 &quot;3.2. JSON Serialization&quot; it states:<br>
<br></blockquote><div>(snip)</div><div>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex;">
Does this mean that an LLSD real type with a value of -Infinity needs to be=
 converted to a JSON string, and would be decoded on the receiving side as =
an LLSD string with value &quot;-Infinity&quot; (that happens to have a val=
id conversion to an LLSD real)? ECMA-262 does not support Infinity, NaN, et=
c. for the JSON &#39;number&#39; type so it looks like we need to transmit =
those values as strings.<br>
</blockquote><div><br></div>That looks like a reasonable interpretation/sug=
gestion to me.=C2=A0</div><div class=3D"gmail_quote"><br></div><div class=
=3D"gmail_quote">While we&#39;re nitpicking this part of the spec:</div><di=
v class=3D"gmail_quote">
<br></div><div class=3D"gmail_quote">* The ABNF for non-special real number=
s is pretty b0rked if I&#39;m reading it correctly. (The exponent is non-op=
tional, negative numbers are not productions, &#39;0.00&#39; is forbidden, =
etc) I&#39;ve mentioned this to Mark Lentczner off-list.</div>
</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">* are=
 &#39;+Zero&#39; and &#39;-Zero&#39; really preferable over &#39;0.0&#39; a=
nd &#39;-0.0&#39; ? Who uses them?</div><div class=3D"gmail_quote"><br></di=
v>
<div class=3D"gmail_quote">* should &#39;Infinity&#39; (sans-+) be consider=
ed valid? how about &#39;NaN&#39; (no &#39;S&#39; or &#39;Q&#39;)?=C2=A0</d=
iv><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">* was th=
is all just a conspiracy by the draft authors to get us talking about their=
 alter egos?</div>
<div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote"><br></div>

--00c09f8de5392393690485f1615e--

From ohmeadhbh@gmail.com  Thu May  6 11:49:30 2010
Return-Path: <ohmeadhbh@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 575DE28C102 for <vwrap@core3.amsl.com>; Thu,  6 May 2010 11:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.409
X-Spam-Level: 
X-Spam-Status: No, score=-1.409 tagged_above=-999 required=5 tests=[AWL=-0.669, BAYES_20=-0.74]
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 qX98mYvzJeNq for <vwrap@core3.amsl.com>; Thu,  6 May 2010 11:49:29 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 13A7928C0FD for <vwrap@ietf.org>; Thu,  6 May 2010 11:49:28 -0700 (PDT)
Received: by vws9 with SMTP id 9so288329vws.31 for <vwrap@ietf.org>; Thu, 06 May 2010 11:49:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=6NZxegmXOVKxieuvaeOyth+IaIx9orspkUsu0gnGzsw=; b=wohXrQgDEZjv5bDF24kBWT1aODpCIL+sRjPeQdFa5R5Q0F3LWUJtOlgoNWoT88Df8o ksSnxt8nX/eO2L6PJZEqovmzPVDESUyQ96BrehYfek7AsZr20PRpmrcUQcSsmTjZ/aDh MmwuKzje8NDW7s/d2Cs7ymYShTlDKlOEGTDto=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=q8CW70JZYvwY+gAUiO5XBayjnH6t77D8YthEm00tGKB+CjqkTG6U8bedUr6e6Bx43L aichbhti4NaXRrCUVgSEGM3oCtKGnMKRrMsTpPAKJhiuudfuKPfmo6qE4B9pw9tXX83N A/8yrXCK8hKaVZwpAZv9Cgd1X3xQOH9KykUHc=
Received: by 10.229.190.209 with SMTP id dj17mr5672385qcb.52.1273171746735;  Thu, 06 May 2010 11:49:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.24.142 with HTTP; Thu, 6 May 2010 11:48:46 -0700 (PDT)
In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com>
References: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com>
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Thu, 6 May 2010 11:48:46 -0700
Message-ID: <r2nb325928b1005061148ke3d86895g6c4fbf1bb1860a8c@mail.gmail.com>
To: "Hurliman, John" <john.hurliman@intel.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "vwrap@ietf.org" <vwrap@ietf.org>
Subject: Re: [vwrap] ECMA-262 and the Real LLSD type
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 18:49:30 -0000

blergh. i wrote that to aggressively support IEEE 754 which includes
several "exceptional" values like plus/minus infinity, signed zero,
NaN, etc. there ARE binary encodings for these numbers, so binary
serialization shouldn't be a problem.

i wonder if it makes sense to say that if you have to transmit an
exceptional IEEE 754 value, you send it as a string instead of a
JSON-number. that way when you do the equivalent of:

llsd_value.asReal();

it would "do the right thing" and convert the string to a real value.
this would require us to have a wrapper class to hang the asReal()
method off, which i know some on this list wanted to try to avoid.

also.. what do current JSON implementations do if you give it
something like a -Infinity? instead of a real?

-cheers
-meadhbh
--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com



On Thu, May 6, 2010 at 10:36 AM, Hurliman, John <john.hurliman@intel.com> w=
rote:
> In draft-hamrick-llsd-00 "3.2. JSON Serialization" it states:
>
> =A0 Real =A0LLSD 'Real' values are represented by the JSON non-terminal '=
number'.
>
> Then later in "Appendix A. ABNF of Real Values" it lists a series of stri=
ngs that can be converted into real values:
>
> =A0 negative-infinity =3D =A0%x2D.49.6E.66.69,6E.69.74.79 =A0 ; "-Infinit=
y"
> =A0 negative-zero =A0 =A0 =3D =A0%x2D.5A.65.72.6F =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 ; "-Zero"
> =A0 zero =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D =A0%x30.2E.30 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 ; "0.0"
> =A0 positive-zero =A0 =A0 =3D =A0%x2B.5A.65.72.6F =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 ; "+Zero"
> =A0 positive-infinity =3D =A0%x2B.49.6E.66.69,6E.69.74.79 =A0 ; "+Infinit=
y"
> =A0 signaling-nan =A0 =A0 =A0 =3D =A0%4E.61.4E.53 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 ; "NaNS"
> =A0 quiet-nan =A0 =A0 =A0 =A0 =3D =A0%4E.61.4E.51 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 ; "NaNQ"
>
> Does this mean that an LLSD real type with a value of -Infinity needs to =
be converted to a JSON string, and would be decoded on the receiving side a=
s an LLSD string with value "-Infinity" (that happens to have a valid conve=
rsion to an LLSD real)? ECMA-262 does not support Infinity, NaN, etc. for t=
he JSON 'number' type so it looks like we need to transmit those values as =
strings.
>
> John
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>

From ohmeadhbh@gmail.com  Thu May  6 11:51:33 2010
Return-Path: <ohmeadhbh@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6AE728C125 for <vwrap@core3.amsl.com>; Thu,  6 May 2010 11:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.79
X-Spam-Level: 
X-Spam-Status: No, score=-0.79 tagged_above=-999 required=5 tests=[AWL=-1.205,  BAYES_40=-0.185, J_CHICKENPOX_14=0.6]
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 xa4zQMUMCMu7 for <vwrap@core3.amsl.com>; Thu,  6 May 2010 11:51:33 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 6ACAF28C148 for <vwrap@ietf.org>; Thu,  6 May 2010 11:51:31 -0700 (PDT)
Received: by gyh4 with SMTP id 4so192015gyh.31 for <vwrap@ietf.org>; Thu, 06 May 2010 11:51:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=b7WwKggapSkl2MjCBHR3SHasYbcN0aoeEbAljSjdtDs=; b=E9lIEIRbVPtwriS7+rz5AfUrpg+zJR/3p4CTLyXR/13xC2nxJLHnsfYoDCkpGHTF4V prZcC49z11nB/N58AClo8XcZy/IF164h+lrUvlHW/8XjLJb1LszWXdJY3s1yRGs0/z3u JO5NHNGrCUTjWR1UqhbeQgKArcMrE73FTaOeM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=MrqRIHT3eDuyrBOLuUgghcns2p8EADdmcnzLgAH4uW5TALsDaYZdc1rQRdPwQkfftA lN8ajTakFt2zgsll51GPfwllf/b4HdVc6UsgXDTlf6uKll/MddtyTZG9V7eXVlqN2Dfc d87BwCovB8AHecdnoimKv+vEYR6npd+ReigDE=
Received: by 10.229.227.68 with SMTP id iz4mr4079110qcb.44.1273171865192; Thu,  06 May 2010 11:51:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.24.142 with HTTP; Thu, 6 May 2010 11:50:45 -0700 (PDT)
In-Reply-To: <v2jf72742de1005061147qad927bb3p9c268fc18b1d0995@mail.gmail.com>
References: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com> <v2jf72742de1005061147qad927bb3p9c268fc18b1d0995@mail.gmail.com>
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Thu, 6 May 2010 11:50:45 -0700
Message-ID: <l2ub325928b1005061150qea5a2a84u15f3f0e06e1452f@mail.gmail.com>
To: Joshua Bell <josh@lindenlab.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "vwrap@ietf.org" <vwrap@ietf.org>
Subject: Re: [vwrap] ECMA-262 and the Real LLSD type
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 18:51:33 -0000

* i think we got the textual values from XDR.
* yes, i chuckled a bit at the thought of embedding my linden name in
a standard.
--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com



On Thu, May 6, 2010 at 11:47 AM, Joshua Bell <josh@lindenlab.com> wrote:
> ("from the floor")
> On Thu, May 6, 2010 at 10:36 AM, Hurliman, John <john.hurliman@intel.com>
> wrote:
>>
>> In draft-hamrick-llsd-00 "3.2. JSON Serialization" it states:
>>
> (snip)
>
>>
>> Does this mean that an LLSD real type with a value of -Infinity needs to
>> be converted to a JSON string, and would be decoded on the receiving side as
>> an LLSD string with value "-Infinity" (that happens to have a valid
>> conversion to an LLSD real)? ECMA-262 does not support Infinity, NaN, etc.
>> for the JSON 'number' type so it looks like we need to transmit those values
>> as strings.
>
> That looks like a reasonable interpretation/suggestion to me.
> While we're nitpicking this part of the spec:
> * The ABNF for non-special real numbers is pretty b0rked if I'm reading it
> correctly. (The exponent is non-optional, negative numbers are not
> productions, '0.00' is forbidden, etc) I've mentioned this to Mark Lentczner
> off-list.
> * are '+Zero' and '-Zero' really preferable over '0.0' and '-0.0' ? Who uses
> them?
> * should 'Infinity' (sans-+) be considered valid? how about 'NaN' (no 'S' or
> 'Q')?
> * was this all just a conspiracy by the draft authors to get us talking
> about their alter egos?
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
>

From ohmeadhbh@gmail.com  Thu May  6 12:07:51 2010
Return-Path: <ohmeadhbh@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE0873A697C for <vwrap@core3.amsl.com>; Thu,  6 May 2010 12:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.226
X-Spam-Level: 
X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=0.373,  BAYES_00=-2.599]
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 8jo0ddqXMz6C for <vwrap@core3.amsl.com>; Thu,  6 May 2010 12:07:50 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 590343A6902 for <vwrap@ietf.org>; Thu,  6 May 2010 12:07:50 -0700 (PDT)
Received: by vws9 with SMTP id 9so308561vws.31 for <vwrap@ietf.org>; Thu, 06 May 2010 12:07:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=GOA7t0HUUgyD6KW9ZvnaoaSHdnMIfQKuADMFZnK3G78=; b=piWnuS16UDUCEBCMsqx/I0HD7Fz0VOyEhHKkL/50txmDpHzpndaGn03zvrtzjESLxN rS1IMhl1dioDNf1+VoYckgTIIBSWtapGNL+EsvTsH86XLPgyise0fGC0xCk0c8kr9Pnc 6RZz8oRhUO+mUsbA9k9hw3VNxB6ZYNiI1nI7g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=bpvMqV4ZXfZ5ljXw1xCCZtN+RFkZJS7BjG2tS5858udlTCRQ3iZvX0vIjdaIkClxAi 8391ErScvxFiWTEn70CVJocMMGom41mZt+SGcgDKHIW9KL0RMZVWibwye5x6xWCOnXHK refyEZ+0wbQOnYTavRtyWA7TKUL5zztANob0w=
Received: by 10.229.28.137 with SMTP id m9mr5744802qcc.21.1273172855501; Thu,  06 May 2010 12:07:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.24.142 with HTTP; Thu, 6 May 2010 12:07:12 -0700 (PDT)
In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com>
References: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com>
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Thu, 6 May 2010 12:07:12 -0700
Message-ID: <n2ob325928b1005061207l186eec38w90cf2ad343c13c6b@mail.gmail.com>
To: "Hurliman, John" <john.hurliman@intel.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "vwrap@ietf.org" <vwrap@ietf.org>
Subject: Re: [vwrap] ECMA-262 and the Real LLSD type
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 19:07:52 -0000

hmm... the ecmascript 5.0 spec seems to imply the string "-Infinity"
is a valid expression of a number, but note 4 on page 217 of the spec
implies that in JSON, you don't get exceptional values like Infinity
or NaN. or rather, both are represented as nulls.

it could be possible to encode all exceptional real values to null,
but when they're deserialized, there would be no way to tell which
exceptional value it was. so you could serialize a value that's
infinity, and deserialize something taht's NaN. but, in theory, this
should be copacetic for JSON parsers.

or... we could layer something on top of JSON to preserve the NaNs and
Infinities. we could come up with a standard way of representing these
values as strings or binaries. (if strings, then the simple strings
listed in the draft. if binaries, maybe the binary patterns in 754
that represent them.) but this will require asReal() and serialize()
methods in LLIDL libraries to understand the usage.

or we could punt and pretend negative infinities don't exist.

ideas? preferences? john, you're out in front as an implementer. what
works for you?

-cheers
-meadhbh
--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com



On Thu, May 6, 2010 at 10:36 AM, Hurliman, John <john.hurliman@intel.com> w=
rote:
> In draft-hamrick-llsd-00 "3.2. JSON Serialization" it states:
>
> =A0 Real =A0LLSD 'Real' values are represented by the JSON non-terminal '=
number'.
>
> Then later in "Appendix A. ABNF of Real Values" it lists a series of stri=
ngs that can be converted into real values:
>
> =A0 negative-infinity =3D =A0%x2D.49.6E.66.69,6E.69.74.79 =A0 ; "-Infinit=
y"
> =A0 negative-zero =A0 =A0 =3D =A0%x2D.5A.65.72.6F =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 ; "-Zero"
> =A0 zero =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D =A0%x30.2E.30 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 ; "0.0"
> =A0 positive-zero =A0 =A0 =3D =A0%x2B.5A.65.72.6F =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 ; "+Zero"
> =A0 positive-infinity =3D =A0%x2B.49.6E.66.69,6E.69.74.79 =A0 ; "+Infinit=
y"
> =A0 signaling-nan =A0 =A0 =A0 =3D =A0%4E.61.4E.53 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 ; "NaNS"
> =A0 quiet-nan =A0 =A0 =A0 =A0 =3D =A0%4E.61.4E.51 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 ; "NaNQ"
>
> Does this mean that an LLSD real type with a value of -Infinity needs to =
be converted to a JSON string, and would be decoded on the receiving side a=
s an LLSD string with value "-Infinity" (that happens to have a valid conve=
rsion to an LLSD real)? ECMA-262 does not support Infinity, NaN, etc. for t=
he JSON 'number' type so it looks like we need to transmit those values as =
strings.
>
> John
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>

From ohmeadhbh@gmail.com  Thu May  6 12:38:21 2010
Return-Path: <ohmeadhbh@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 054B93A6C19 for <vwrap@core3.amsl.com>; Thu,  6 May 2010 12:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.247
X-Spam-Level: 
X-Spam-Status: No, score=-2.247 tagged_above=-999 required=5 tests=[AWL=0.352,  BAYES_00=-2.599]
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 V0lXdt-+5TGL for <vwrap@core3.amsl.com>; Thu,  6 May 2010 12:38:20 -0700 (PDT)
Received: from mail-qy0-f197.google.com (mail-qy0-f197.google.com [209.85.221.197]) by core3.amsl.com (Postfix) with ESMTP id D4E253A6C15 for <vwrap@ietf.org>; Thu,  6 May 2010 12:38:19 -0700 (PDT)
Received: by qyk35 with SMTP id 35so445829qyk.15 for <vwrap@ietf.org>; Thu, 06 May 2010 12:38:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=btWjWuTe36N1l9thmVwb9eei2DKFtiCP+w6wKDCBW8U=; b=qHCIYH2Os1BuBlK9yVyw/p0wh5IeTXzRn8+n7uCKjvhzhgqin2v96cw28ssfSAY6gh 9sBoXR9jzy1Bstc9qfT7FgRCZ8DEQWVoPbSRLU1o8q64ceKXxJsuIXlPnuyHTZ5nQrcD imty0R+U+C/6FV8CFG3auzHTQRGx3o2gyJb1Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=xTFx0cy39fY/9/MM5kSAHLQUkDO7OuilwNQ8n2fc0BQfWRxgWNO38tuLNbDxc2B6xF DCCngXoBGighzdYOWKTNWb3hgimpgIbzqHMBZ38jf63pq2F43mvxNaBiXkzWvfNSQX77 yZTrZSDXnP9MdKSdEg8tLzqGHxxzb3HRzaJL0=
Received: by 10.229.231.144 with SMTP id jq16mr4208183qcb.53.1273174683242;  Thu, 06 May 2010 12:38:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.24.142 with HTTP; Thu, 6 May 2010 12:37:43 -0700 (PDT)
In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com>
References: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com>
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Thu, 6 May 2010 12:37:43 -0700
Message-ID: <z2jb325928b1005061237q9c08d062v25e43996c964839f@mail.gmail.com>
To: "Hurliman, John" <john.hurliman@intel.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "vwrap@ietf.org" <vwrap@ietf.org>
Subject: Re: [vwrap] ECMA-262 and the Real LLSD type
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 19:38:21 -0000

k. so i pinged doug crockford about it. his response was that JSON
wants to be independent of any floating point standard, and thus only
represents finite numbers.

so... a) it's not a mistake or an oversight that you can't represent
NaNs as JSON-Numbers and b) even if it somehow worked in current
implementations, it's not the intent of the JSON designers, so, it may
not work in the future.

so do we know how important it is to represent each of the distinct
non-finite reals?

-cheers
-meadhbh
--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com



On Thu, May 6, 2010 at 10:36 AM, Hurliman, John <john.hurliman@intel.com> w=
rote:
> In draft-hamrick-llsd-00 "3.2. JSON Serialization" it states:
>
> =A0 Real =A0LLSD 'Real' values are represented by the JSON non-terminal '=
number'.
>
> Then later in "Appendix A. ABNF of Real Values" it lists a series of stri=
ngs that can be converted into real values:
>
> =A0 negative-infinity =3D =A0%x2D.49.6E.66.69,6E.69.74.79 =A0 ; "-Infinit=
y"
> =A0 negative-zero =A0 =A0 =3D =A0%x2D.5A.65.72.6F =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 ; "-Zero"
> =A0 zero =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D =A0%x30.2E.30 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 ; "0.0"
> =A0 positive-zero =A0 =A0 =3D =A0%x2B.5A.65.72.6F =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 ; "+Zero"
> =A0 positive-infinity =3D =A0%x2B.49.6E.66.69,6E.69.74.79 =A0 ; "+Infinit=
y"
> =A0 signaling-nan =A0 =A0 =A0 =3D =A0%4E.61.4E.53 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 ; "NaNS"
> =A0 quiet-nan =A0 =A0 =A0 =A0 =3D =A0%4E.61.4E.51 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 ; "NaNQ"
>
> Does this mean that an LLSD real type with a value of -Infinity needs to =
be converted to a JSON string, and would be decoded on the receiving side a=
s an LLSD string with value "-Infinity" (that happens to have a valid conve=
rsion to an LLSD real)? ECMA-262 does not support Infinity, NaN, etc. for t=
he JSON 'number' type so it looks like we need to transmit those values as =
strings.
>
> John
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>

From josh@lindenlab.com  Thu May  6 13:51:12 2010
Return-Path: <josh@lindenlab.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D9ED3A6C2B for <vwrap@core3.amsl.com>; Thu,  6 May 2010 13:51:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.118
X-Spam-Level: 
X-Spam-Status: No, score=0.118 tagged_above=-999 required=5 tests=[AWL=0.605,  BAYES_05=-1.11, 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 D2D6+FOzEtJ2 for <vwrap@core3.amsl.com>; Thu,  6 May 2010 13:51:10 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 2005E3A6C5F for <vwrap@ietf.org>; Thu,  6 May 2010 13:48:39 -0700 (PDT)
Received: by vws9 with SMTP id 9so416767vws.31 for <vwrap@ietf.org>; Thu, 06 May 2010 13:48:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.108.7 with SMTP id d7mr1234447vcp.161.1273178903486; Thu,  06 May 2010 13:48:23 -0700 (PDT)
Received: by 10.220.73.13 with HTTP; Thu, 6 May 2010 13:48:23 -0700 (PDT)
In-Reply-To: <z2jb325928b1005061237q9c08d062v25e43996c964839f@mail.gmail.com>
References: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com> <z2jb325928b1005061237q9c08d062v25e43996c964839f@mail.gmail.com>
Date: Thu, 6 May 2010 13:48:23 -0700
Message-ID: <m2xf72742de1005061348h5f0a246doad547c752272fe5@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: "vwrap@ietf.org" <vwrap@ietf.org>
Content-Type: multipart/alternative; boundary=00c09f971b8b4722140485f3107e
Subject: Re: [vwrap] ECMA-262 and the Real LLSD type
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 20:51:12 -0000

--00c09f971b8b4722140485f3107e
Content-Type: text/plain; charset=UTF-8

I did some playing in an ECMAScript implementation of LLSD, following John's
suggestions of serializing NaN, +/- Infinity, and also negative zero, as
strings when serializing to JSON. Round-tripping works like a charm,
assuming of course that you're testing the results using an "asReal"
coercion that follows the same logic, which an LLSD implementation should
be.

Crockford's http://www.json.org/js.html page even hints at this approach at
the bottom, suggesting that non-finite values could be serialized to JSON as
strings.

On Thu, May 6, 2010 at 12:37 PM, Meadhbh Hamrick <ohmeadhbh@gmail.com>wrote:

> k. so i pinged doug crockford about it. his response was that JSON
> wants to be independent of any floating point standard, and thus only
> represents finite numbers.
>
> so... a) it's not a mistake or an oversight that you can't represent
> NaNs as JSON-Numbers and b) even if it somehow worked in current
> implementations, it's not the intent of the JSON designers, so, it may
> not work in the future.
>
> so do we know how important it is to represent each of the distinct
> non-finite reals?
>
> -cheers
> -meadhbh
> --
> meadhbh hamrick * it's pronounced "maeve"
> @OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com
>
>
>
> On Thu, May 6, 2010 at 10:36 AM, Hurliman, John <john.hurliman@intel.com>
> wrote:
> > In draft-hamrick-llsd-00 "3.2. JSON Serialization" it states:
> >
> >   Real  LLSD 'Real' values are represented by the JSON non-terminal
> 'number'.
> >
> > Then later in "Appendix A. ABNF of Real Values" it lists a series of
> strings that can be converted into real values:
> >
> >   negative-infinity =  %x2D.49.6E.66.69,6E.69.74.79   ; "-Infinity"
> >   negative-zero     =  %x2D.5A.65.72.6F               ; "-Zero"
> >   zero              =  %x30.2E.30                     ; "0.0"
> >   positive-zero     =  %x2B.5A.65.72.6F               ; "+Zero"
> >   positive-infinity =  %x2B.49.6E.66.69,6E.69.74.79   ; "+Infinity"
> >   signaling-nan       =  %4E.61.4E.53                   ; "NaNS"
> >   quiet-nan         =  %4E.61.4E.51                   ; "NaNQ"
> >
> > Does this mean that an LLSD real type with a value of -Infinity needs to
> be converted to a JSON string, and would be decoded on the receiving side as
> an LLSD string with value "-Infinity" (that happens to have a valid
> conversion to an LLSD real)? ECMA-262 does not support Infinity, NaN, etc.
> for the JSON 'number' type so it looks like we need to transmit those values
> as strings.
> >
> > John
> > _______________________________________________
> > vwrap mailing list
> > vwrap@ietf.org
> > https://www.ietf.org/mailman/listinfo/vwrap
> >
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>

--00c09f971b8b4722140485f3107e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I did some playing in an ECMAScript implementation of LLSD, following John&=
#39;s suggestions of serializing NaN, +/- Infinity, and also negative zero,=
 as strings when serializing to JSON. Round-tripping works like a charm, as=
suming of course that you&#39;re testing the results using an &quot;asReal&=
quot; coercion that follows the same logic, which an LLSD implementation sh=
ould be.<div>
<br></div><div>Crockford&#39;s <a href=3D"http://www.json.org/js.html">http=
://www.json.org/js.html</a>=C2=A0page even hints at this approach at the bo=
ttom, suggesting that non-finite values could be serialized to JSON as stri=
ngs.<br>
<div><div><br><div class=3D"gmail_quote">On Thu, May 6, 2010 at 12:37 PM, M=
eadhbh Hamrick <span dir=3D"ltr">&lt;<a href=3D"mailto:ohmeadhbh@gmail.com"=
>ohmeadhbh@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
;">
k. so i pinged doug crockford about it. his response was that JSON<br>
wants to be independent of any floating point standard, and thus only<br>
represents finite numbers.<br>
<br>
so... a) it&#39;s not a mistake or an oversight that you can&#39;t represen=
t<br>
NaNs as JSON-Numbers and b) even if it somehow worked in current<br>
implementations, it&#39;s not the intent of the JSON designers, so, it may<=
br>
not work in the future.<br>
<br>
so do we know how important it is to represent each of the distinct<br>
non-finite reals?<br>
<div class=3D"im"><br>
-cheers<br>
-meadhbh<br>
--<br>
meadhbh hamrick * it&#39;s pronounced &quot;maeve&quot;<br>
@OhMeadhbh * <a href=3D"http://meadhbh.org/" target=3D"_blank">http://meadh=
bh.org/</a> * <a href=3D"mailto:OhMeadhbh@gmail.com">OhMeadhbh@gmail.com</a=
><br>
<br>
<br>
<br>
On Thu, May 6, 2010 at 10:36 AM, Hurliman, John &lt;<a href=3D"mailto:john.=
hurliman@intel.com">john.hurliman@intel.com</a>&gt; wrote:<br>
</div><div><div></div><div class=3D"h5">&gt; In draft-hamrick-llsd-00 &quot=
;3.2. JSON Serialization&quot; it states:<br>
&gt;<br>
&gt; =C2=A0 Real =C2=A0LLSD &#39;Real&#39; values are represented by the JS=
ON non-terminal &#39;number&#39;.<br>
&gt;<br>
&gt; Then later in &quot;Appendix A. ABNF of Real Values&quot; it lists a s=
eries of strings that can be converted into real values:<br>
&gt;<br>
&gt; =C2=A0 negative-infinity =3D =C2=A0%x2D.49.6E.66.69,6E.69.74.79 =C2=A0=
 ; &quot;-Infinity&quot;<br>
&gt; =C2=A0 negative-zero =C2=A0 =C2=A0 =3D =C2=A0%x2D.5A.65.72.6F =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ; &quot;-Zero&quot;<br>
&gt; =C2=A0 zero =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D =C2=A0=
%x30.2E.30 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 ; &quot;0.0&quot;<br>
&gt; =C2=A0 positive-zero =C2=A0 =C2=A0 =3D =C2=A0%x2B.5A.65.72.6F =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ; &quot;+Zero&quot;<br>
&gt; =C2=A0 positive-infinity =3D =C2=A0%x2B.49.6E.66.69,6E.69.74.79 =C2=A0=
 ; &quot;+Infinity&quot;<br>
&gt; =C2=A0 signaling-nan =C2=A0 =C2=A0 =C2=A0 =3D =C2=A0%4E.61.4E.53 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ; &quot;NaNS&qu=
ot;<br>
&gt; =C2=A0 quiet-nan =C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D =C2=A0%4E.61.4E.51 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ; &quot;NaNQ=
&quot;<br>
&gt;<br>
&gt; Does this mean that an LLSD real type with a value of -Infinity needs =
to be converted to a JSON string, and would be decoded on the receiving sid=
e as an LLSD string with value &quot;-Infinity&quot; (that happens to have =
a valid conversion to an LLSD real)? ECMA-262 does not support Infinity, Na=
N, etc. for the JSON &#39;number&#39; type so it looks like we need to tran=
smit those values as strings.<br>

&gt;<br>
&gt; John<br>
&gt; _______________________________________________<br>
&gt; vwrap mailing list<br>
&gt; <a href=3D"mailto:vwrap@ietf.org">vwrap@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
&gt;<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
</div></div></blockquote></div><br></div></div></div>

--00c09f971b8b4722140485f3107e--

From john.hurliman@intel.com  Thu May  6 13:55:02 2010
Return-Path: <john.hurliman@intel.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D10A3A6A98 for <vwrap@core3.amsl.com>; Thu,  6 May 2010 13:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level: 
X-Spam-Status: No, score=-7.099 tagged_above=-999 required=5 tests=[AWL=-0.501, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 JkPjMNxSuexP for <vwrap@core3.amsl.com>; Thu,  6 May 2010 13:55:01 -0700 (PDT)
Received: from mga14.intel.com (mga14.intel.com [143.182.124.37]) by core3.amsl.com (Postfix) with ESMTP id EFBE83A6A08 for <vwrap@ietf.org>; Thu,  6 May 2010 13:54:57 -0700 (PDT)
Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga102.ch.intel.com with ESMTP; 06 May 2010 13:54:44 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.52,343,1270450800";  d="scan'208,217";a="274229269"
Received: from rrsmsx602.amr.corp.intel.com ([10.31.0.33]) by azsmga001.ch.intel.com with ESMTP; 06 May 2010 13:54:34 -0700
Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx602.amr.corp.intel.com ([10.31.0.33]) with mapi; Thu, 6 May 2010 14:54:34 -0600
From: "Hurliman, John" <john.hurliman@intel.com>
To: Joshua Bell <josh@lindenlab.com>, "vwrap@ietf.org" <vwrap@ietf.org>
Date: Thu, 6 May 2010 14:54:32 -0600
Thread-Topic: [vwrap] ECMA-262 and the Real LLSD type
Thread-Index: AcrtXdlUCAyn0uXRSVCLCAuabFFbFQAAGzJQ
Message-ID: <62BFE5680C037E4DA0B0A08946C0933DCE425C2A@rrsmsx506.amr.corp.intel.com>
References: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com> <z2jb325928b1005061237q9c08d062v25e43996c964839f@mail.gmail.com> <m2xf72742de1005061348h5f0a246doad547c752272fe5@mail.gmail.com>
In-Reply-To: <m2xf72742de1005061348h5f0a246doad547c752272fe5@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_62BFE5680C037E4DA0B0A08946C0933DCE425C2Arrsmsx506amrcor_"
MIME-Version: 1.0
Subject: Re: [vwrap] ECMA-262 and the Real LLSD type
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 20:55:02 -0000

--_000_62BFE5680C037E4DA0B0A08946C0933DCE425C2Arrsmsx506amrcor_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmW0gZmluZSB3aXRoIHRoYXQgYXBwcm9hY2guDQpKb2huDQoNCkZyb206IHZ3cmFwLWJvdW5j
ZXNAaWV0Zi5vcmcgW21haWx0bzp2d3JhcC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2Yg
Sm9zaHVhIEJlbGwNClNlbnQ6IFRodXJzZGF5LCBNYXkgMDYsIDIwMTAgMTo0OCBQTQ0KVG86IHZ3
cmFwQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW3Z3cmFwXSBFQ01BLTI2MiBhbmQgdGhlIFJlYWwg
TExTRCB0eXBlDQoNCkkgZGlkIHNvbWUgcGxheWluZyBpbiBhbiBFQ01BU2NyaXB0IGltcGxlbWVu
dGF0aW9uIG9mIExMU0QsIGZvbGxvd2luZyBKb2huJ3Mgc3VnZ2VzdGlvbnMgb2Ygc2VyaWFsaXpp
bmcgTmFOLCArLy0gSW5maW5pdHksIGFuZCBhbHNvIG5lZ2F0aXZlIHplcm8sIGFzIHN0cmluZ3Mg
d2hlbiBzZXJpYWxpemluZyB0byBKU09OLiBSb3VuZC10cmlwcGluZyB3b3JrcyBsaWtlIGEgY2hh
cm0sIGFzc3VtaW5nIG9mIGNvdXJzZSB0aGF0IHlvdSdyZSB0ZXN0aW5nIHRoZSByZXN1bHRzIHVz
aW5nIGFuICJhc1JlYWwiIGNvZXJjaW9uIHRoYXQgZm9sbG93cyB0aGUgc2FtZSBsb2dpYywgd2hp
Y2ggYW4gTExTRCBpbXBsZW1lbnRhdGlvbiBzaG91bGQgYmUuDQoNCkNyb2NrZm9yZCdzIGh0dHA6
Ly93d3cuanNvbi5vcmcvanMuaHRtbCBwYWdlIGV2ZW4gaGludHMgYXQgdGhpcyBhcHByb2FjaCBh
dCB0aGUgYm90dG9tLCBzdWdnZXN0aW5nIHRoYXQgbm9uLWZpbml0ZSB2YWx1ZXMgY291bGQgYmUg
c2VyaWFsaXplZCB0byBKU09OIGFzIHN0cmluZ3MuDQoNCk9uIFRodSwgTWF5IDYsIDIwMTAgYXQg
MTI6MzcgUE0sIE1lYWRoYmggSGFtcmljayA8b2htZWFkaGJoQGdtYWlsLmNvbTxtYWlsdG86b2ht
ZWFkaGJoQGdtYWlsLmNvbT4+IHdyb3RlOg0Kay4gc28gaSBwaW5nZWQgZG91ZyBjcm9ja2ZvcmQg
YWJvdXQgaXQuIGhpcyByZXNwb25zZSB3YXMgdGhhdCBKU09ODQp3YW50cyB0byBiZSBpbmRlcGVu
ZGVudCBvZiBhbnkgZmxvYXRpbmcgcG9pbnQgc3RhbmRhcmQsIGFuZCB0aHVzIG9ubHkNCnJlcHJl
c2VudHMgZmluaXRlIG51bWJlcnMuDQoNCnNvLi4uIGEpIGl0J3Mgbm90IGEgbWlzdGFrZSBvciBh
biBvdmVyc2lnaHQgdGhhdCB5b3UgY2FuJ3QgcmVwcmVzZW50DQpOYU5zIGFzIEpTT04tTnVtYmVy
cyBhbmQgYikgZXZlbiBpZiBpdCBzb21laG93IHdvcmtlZCBpbiBjdXJyZW50DQppbXBsZW1lbnRh
dGlvbnMsIGl0J3Mgbm90IHRoZSBpbnRlbnQgb2YgdGhlIEpTT04gZGVzaWduZXJzLCBzbywgaXQg
bWF5DQpub3Qgd29yayBpbiB0aGUgZnV0dXJlLg0KDQpzbyBkbyB3ZSBrbm93IGhvdyBpbXBvcnRh
bnQgaXQgaXMgdG8gcmVwcmVzZW50IGVhY2ggb2YgdGhlIGRpc3RpbmN0DQpub24tZmluaXRlIHJl
YWxzPw0KDQotY2hlZXJzDQotbWVhZGhiaA0KLS0NCm1lYWRoYmggaGFtcmljayAqIGl0J3MgcHJv
bm91bmNlZCAibWFldmUiDQpAT2hNZWFkaGJoICogaHR0cDovL21lYWRoYmgub3JnLyAqIE9oTWVh
ZGhiaEBnbWFpbC5jb208bWFpbHRvOk9oTWVhZGhiaEBnbWFpbC5jb20+DQoNCg0KDQpPbiBUaHUs
IE1heSA2LCAyMDEwIGF0IDEwOjM2IEFNLCBIdXJsaW1hbiwgSm9obiA8am9obi5odXJsaW1hbkBp
bnRlbC5jb208bWFpbHRvOmpvaG4uaHVybGltYW5AaW50ZWwuY29tPj4gd3JvdGU6DQo+IEluIGRy
YWZ0LWhhbXJpY2stbGxzZC0wMCAiMy4yLiBKU09OIFNlcmlhbGl6YXRpb24iIGl0IHN0YXRlczoN
Cj4NCj4gICBSZWFsICBMTFNEICdSZWFsJyB2YWx1ZXMgYXJlIHJlcHJlc2VudGVkIGJ5IHRoZSBK
U09OIG5vbi10ZXJtaW5hbCAnbnVtYmVyJy4NCj4NCj4gVGhlbiBsYXRlciBpbiAiQXBwZW5kaXgg
QS4gQUJORiBvZiBSZWFsIFZhbHVlcyIgaXQgbGlzdHMgYSBzZXJpZXMgb2Ygc3RyaW5ncyB0aGF0
IGNhbiBiZSBjb252ZXJ0ZWQgaW50byByZWFsIHZhbHVlczoNCj4NCj4gICBuZWdhdGl2ZS1pbmZp
bml0eSA9ICAleDJELjQ5LjZFLjY2LjY5LDZFLjY5Ljc0Ljc5ICAgOyAiLUluZmluaXR5Ig0KPiAg
IG5lZ2F0aXZlLXplcm8gICAgID0gICV4MkQuNUEuNjUuNzIuNkYgICAgICAgICAgICAgICA7ICIt
WmVybyINCj4gICB6ZXJvICAgICAgICAgICAgICA9ICAleDMwLjJFLjMwICAgICAgICAgICAgICAg
ICAgICAgOyAiMC4wIg0KPiAgIHBvc2l0aXZlLXplcm8gICAgID0gICV4MkIuNUEuNjUuNzIuNkYg
ICAgICAgICAgICAgICA7ICIrWmVybyINCj4gICBwb3NpdGl2ZS1pbmZpbml0eSA9ICAleDJCLjQ5
LjZFLjY2LjY5LDZFLjY5Ljc0Ljc5ICAgOyAiK0luZmluaXR5Ig0KPiAgIHNpZ25hbGluZy1uYW4g
ICAgICAgPSAgJTRFLjYxLjRFLjUzICAgICAgICAgICAgICAgICAgIDsgIk5hTlMiDQo+ICAgcXVp
ZXQtbmFuICAgICAgICAgPSAgJTRFLjYxLjRFLjUxICAgICAgICAgICAgICAgICAgIDsgIk5hTlEi
DQo+DQo+IERvZXMgdGhpcyBtZWFuIHRoYXQgYW4gTExTRCByZWFsIHR5cGUgd2l0aCBhIHZhbHVl
IG9mIC1JbmZpbml0eSBuZWVkcyB0byBiZSBjb252ZXJ0ZWQgdG8gYSBKU09OIHN0cmluZywgYW5k
IHdvdWxkIGJlIGRlY29kZWQgb24gdGhlIHJlY2VpdmluZyBzaWRlIGFzIGFuIExMU0Qgc3RyaW5n
IHdpdGggdmFsdWUgIi1JbmZpbml0eSIgKHRoYXQgaGFwcGVucyB0byBoYXZlIGEgdmFsaWQgY29u
dmVyc2lvbiB0byBhbiBMTFNEIHJlYWwpPyBFQ01BLTI2MiBkb2VzIG5vdCBzdXBwb3J0IEluZmlu
aXR5LCBOYU4sIGV0Yy4gZm9yIHRoZSBKU09OICdudW1iZXInIHR5cGUgc28gaXQgbG9va3MgbGlr
ZSB3ZSBuZWVkIHRvIHRyYW5zbWl0IHRob3NlIHZhbHVlcyBhcyBzdHJpbmdzLg0KPg0KPiBKb2hu
DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IHZ3
cmFwIG1haWxpbmcgbGlzdA0KPiB2d3JhcEBpZXRmLm9yZzxtYWlsdG86dndyYXBAaWV0Zi5vcmc+
DQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXANCj4NCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQp2d3JhcCBtYWlsaW5n
IGxpc3QNCnZ3cmFwQGlldGYub3JnPG1haWx0bzp2d3JhcEBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXANCg0K

--_000_62BFE5680C037E4DA0B0A08946C0933DCE425C2Arrsmsx506amrcor_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw
YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z
b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs
b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj
b3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCglj
b2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v
bmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KQHBhZ2UgV29yZFNl
Y3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAx
LjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT48L2hlYWQ+
PGJvZHkgbGFuZz1FTi1VUyBsaW5rPWJsdWUgdmxpbms9cHVycGxlPjxkaXYgY2xhc3M9V29yZFNl
Y3Rpb24xPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPknigJltIGZp
bmUgd2l0aCB0aGF0IGFwcHJvYWNoLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29O
b3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5Kb2huPG86cD48L286cD48L3NwYW4+PC9wPjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQnPjxkaXY+PGRpdiBzdHlsZT0nYm9yZGVy
Om5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBp
biAwaW4nPjxwIGNsYXNzPU1zb05vcm1hbD48Yj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPkZyb206PC9zcGFuPjwvYj48c3Bh
biBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJp
ZiInPiB2d3JhcC1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dndyYXAtYm91bmNlc0BpZXRmLm9y
Z10gPGI+T24gQmVoYWxmIE9mIDwvYj5Kb3NodWEgQmVsbDxicj48Yj5TZW50OjwvYj4gVGh1cnNk
YXksIE1heSAwNiwgMjAxMCAxOjQ4IFBNPGJyPjxiPlRvOjwvYj4gdndyYXBAaWV0Zi5vcmc8YnI+
PGI+U3ViamVjdDo8L2I+IFJlOiBbdndyYXBdIEVDTUEtMjYyIGFuZCB0aGUgUmVhbCBMTFNEIHR5
cGU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD5JIGRpZCBzb21lIHBsYXlpbmcg
aW4gYW4gRUNNQVNjcmlwdCBpbXBsZW1lbnRhdGlvbiBvZiBMTFNELCBmb2xsb3dpbmcgSm9obidz
IHN1Z2dlc3Rpb25zIG9mIHNlcmlhbGl6aW5nIE5hTiwgKy8tIEluZmluaXR5LCBhbmQgYWxzbyBu
ZWdhdGl2ZSB6ZXJvLCBhcyBzdHJpbmdzIHdoZW4gc2VyaWFsaXppbmcgdG8gSlNPTi4gUm91bmQt
dHJpcHBpbmcgd29ya3MgbGlrZSBhIGNoYXJtLCBhc3N1bWluZyBvZiBjb3Vyc2UgdGhhdCB5b3Un
cmUgdGVzdGluZyB0aGUgcmVzdWx0cyB1c2luZyBhbiAmcXVvdDthc1JlYWwmcXVvdDsgY29lcmNp
b24gdGhhdCBmb2xsb3dzIHRoZSBzYW1lIGxvZ2ljLCB3aGljaCBhbiBMTFNEIGltcGxlbWVudGF0
aW9uIHNob3VsZCBiZS48bzpwPjwvbzpwPjwvcD48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48bzpw
PiZuYnNwOzwvbzpwPjwvcD48L2Rpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD5Dcm9ja2ZvcmQn
cyA8YSBocmVmPSJodHRwOi8vd3d3Lmpzb24ub3JnL2pzLmh0bWwiPmh0dHA6Ly93d3cuanNvbi5v
cmcvanMuaHRtbDwvYT4mbmJzcDtwYWdlIGV2ZW4gaGludHMgYXQgdGhpcyBhcHByb2FjaCBhdCB0
aGUgYm90dG9tLCBzdWdnZXN0aW5nIHRoYXQgbm9uLWZpbml0ZSB2YWx1ZXMgY291bGQgYmUgc2Vy
aWFsaXplZCB0byBKU09OIGFzIHN0cmluZ3MuPG86cD48L286cD48L3A+PGRpdj48ZGl2PjxwIGNs
YXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpwPjwvcD48ZGl2PjxwIGNsYXNzPU1zb05vcm1h
bD5PbiBUaHUsIE1heSA2LCAyMDEwIGF0IDEyOjM3IFBNLCBNZWFkaGJoIEhhbXJpY2sgJmx0Ozxh
IGhyZWY9Im1haWx0bzpvaG1lYWRoYmhAZ21haWwuY29tIj5vaG1lYWRoYmhAZ21haWwuY29tPC9h
PiZndDsgd3JvdGU6PG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPmsuIHNvIGkgcGlu
Z2VkIGRvdWcgY3JvY2tmb3JkIGFib3V0IGl0LiBoaXMgcmVzcG9uc2Ugd2FzIHRoYXQgSlNPTjxi
cj53YW50cyB0byBiZSBpbmRlcGVuZGVudCBvZiBhbnkgZmxvYXRpbmcgcG9pbnQgc3RhbmRhcmQs
IGFuZCB0aHVzIG9ubHk8YnI+cmVwcmVzZW50cyBmaW5pdGUgbnVtYmVycy48YnI+PGJyPnNvLi4u
IGEpIGl0J3Mgbm90IGEgbWlzdGFrZSBvciBhbiBvdmVyc2lnaHQgdGhhdCB5b3UgY2FuJ3QgcmVw
cmVzZW50PGJyPk5hTnMgYXMgSlNPTi1OdW1iZXJzIGFuZCBiKSBldmVuIGlmIGl0IHNvbWVob3cg
d29ya2VkIGluIGN1cnJlbnQ8YnI+aW1wbGVtZW50YXRpb25zLCBpdCdzIG5vdCB0aGUgaW50ZW50
IG9mIHRoZSBKU09OIGRlc2lnbmVycywgc28sIGl0IG1heTxicj5ub3Qgd29yayBpbiB0aGUgZnV0
dXJlLjxicj48YnI+c28gZG8gd2Uga25vdyBob3cgaW1wb3J0YW50IGl0IGlzIHRvIHJlcHJlc2Vu
dCBlYWNoIG9mIHRoZSBkaXN0aW5jdDxicj5ub24tZmluaXRlIHJlYWxzPzxvOnA+PC9vOnA+PC9w
PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxicj4tY2hlZXJzPGJyPi1tZWFkaGJoPGJyPi0tPGJy
Pm1lYWRoYmggaGFtcmljayAqIGl0J3MgcHJvbm91bmNlZCAmcXVvdDttYWV2ZSZxdW90Ozxicj5A
T2hNZWFkaGJoICogPGEgaHJlZj0iaHR0cDovL21lYWRoYmgub3JnLyIgdGFyZ2V0PSJfYmxhbmsi
Pmh0dHA6Ly9tZWFkaGJoLm9yZy88L2E+ICogPGEgaHJlZj0ibWFpbHRvOk9oTWVhZGhiaEBnbWFp
bC5jb20iPk9oTWVhZGhiaEBnbWFpbC5jb208L2E+PGJyPjxicj48YnI+PGJyPk9uIFRodSwgTWF5
IDYsIDIwMTAgYXQgMTA6MzYgQU0sIEh1cmxpbWFuLCBKb2huICZsdDs8YSBocmVmPSJtYWlsdG86
am9obi5odXJsaW1hbkBpbnRlbC5jb20iPmpvaG4uaHVybGltYW5AaW50ZWwuY29tPC9hPiZndDsg
d3JvdGU6PG86cD48L286cD48L3A+PC9kaXY+PGRpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD4m
Z3Q7IEluIGRyYWZ0LWhhbXJpY2stbGxzZC0wMCAmcXVvdDszLjIuIEpTT04gU2VyaWFsaXphdGlv
biZxdW90OyBpdCBzdGF0ZXM6PGJyPiZndDs8YnI+Jmd0OyAmbmJzcDsgUmVhbCAmbmJzcDtMTFNE
ICdSZWFsJyB2YWx1ZXMgYXJlIHJlcHJlc2VudGVkIGJ5IHRoZSBKU09OIG5vbi10ZXJtaW5hbCAn
bnVtYmVyJy48YnI+Jmd0Ozxicj4mZ3Q7IFRoZW4gbGF0ZXIgaW4gJnF1b3Q7QXBwZW5kaXggQS4g
QUJORiBvZiBSZWFsIFZhbHVlcyZxdW90OyBpdCBsaXN0cyBhIHNlcmllcyBvZiBzdHJpbmdzIHRo
YXQgY2FuIGJlIGNvbnZlcnRlZCBpbnRvIHJlYWwgdmFsdWVzOjxicj4mZ3Q7PGJyPiZndDsgJm5i
c3A7IG5lZ2F0aXZlLWluZmluaXR5ID0gJm5ic3A7JXgyRC40OS42RS42Ni42OSw2RS42OS43NC43
OSAmbmJzcDsgOyAmcXVvdDstSW5maW5pdHkmcXVvdDs8YnI+Jmd0OyAmbmJzcDsgbmVnYXRpdmUt
emVybyAmbmJzcDsgJm5ic3A7ID0gJm5ic3A7JXgyRC41QS42NS43Mi42RiAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgOyAmcXVvdDstWmVybyZxdW90Ozxi
cj4mZ3Q7ICZuYnNwOyB6ZXJvICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOz0gJm5ic3A7JXgzMC4yRS4zMCAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgOyAmcXVvdDswLjAmcXVv
dDs8YnI+Jmd0OyAmbmJzcDsgcG9zaXRpdmUtemVybyAmbmJzcDsgJm5ic3A7ID0gJm5ic3A7JXgy
Qi41QS42NS43Mi42RiAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgOyAmcXVvdDsrWmVybyZxdW90Ozxicj4mZ3Q7ICZuYnNwOyBwb3NpdGl2ZS1pbmZpbml0
eSA9ICZuYnNwOyV4MkIuNDkuNkUuNjYuNjksNkUuNjkuNzQuNzkgJm5ic3A7IDsgJnF1b3Q7K0lu
ZmluaXR5JnF1b3Q7PGJyPiZndDsgJm5ic3A7IHNpZ25hbGluZy1uYW4gJm5ic3A7ICZuYnNwOyAm
bmJzcDsgPSAmbmJzcDslNEUuNjEuNEUuNTMgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgOyAmcXVvdDtOYU5TJnF1b3Q7PGJyPiZn
dDsgJm5ic3A7IHF1aWV0LW5hbiAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgPSAmbmJzcDsl
NEUuNjEuNEUuNTEgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgOyAmcXVvdDtOYU5RJnF1b3Q7PGJyPiZndDs8YnI+Jmd0OyBEb2Vz
IHRoaXMgbWVhbiB0aGF0IGFuIExMU0QgcmVhbCB0eXBlIHdpdGggYSB2YWx1ZSBvZiAtSW5maW5p
dHkgbmVlZHMgdG8gYmUgY29udmVydGVkIHRvIGEgSlNPTiBzdHJpbmcsIGFuZCB3b3VsZCBiZSBk
ZWNvZGVkIG9uIHRoZSByZWNlaXZpbmcgc2lkZSBhcyBhbiBMTFNEIHN0cmluZyB3aXRoIHZhbHVl
ICZxdW90Oy1JbmZpbml0eSZxdW90OyAodGhhdCBoYXBwZW5zIHRvIGhhdmUgYSB2YWxpZCBjb252
ZXJzaW9uIHRvIGFuIExMU0QgcmVhbCk/IEVDTUEtMjYyIGRvZXMgbm90IHN1cHBvcnQgSW5maW5p
dHksIE5hTiwgZXRjLiBmb3IgdGhlIEpTT04gJ251bWJlcicgdHlwZSBzbyBpdCBsb29rcyBsaWtl
IHdlIG5lZWQgdG8gdHJhbnNtaXQgdGhvc2UgdmFsdWVzIGFzIHN0cmluZ3MuPGJyPiZndDs8YnI+
Jmd0OyBKb2huPGJyPiZndDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX188YnI+Jmd0OyB2d3JhcCBtYWlsaW5nIGxpc3Q8YnI+Jmd0OyA8YSBocmVmPSJtYWls
dG86dndyYXBAaWV0Zi5vcmciPnZ3cmFwQGlldGYub3JnPC9hPjxicj4mZ3Q7IDxhIGhyZWY9Imh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXAiIHRhcmdldD0iX2JsYW5r
Ij5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Z3cmFwPC9hPjxicj4mZ3Q7
PGJyPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPnZ3
cmFwIG1haWxpbmcgbGlzdDxicj48YSBocmVmPSJtYWlsdG86dndyYXBAaWV0Zi5vcmciPnZ3cmFw
QGlldGYub3JnPC9hPjxicj48YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3Z3cmFwIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby92d3JhcDwvYT48bzpwPjwvbzpwPjwvcD48L2Rpdj48L2Rpdj48L2Rpdj48cCBj
bGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48L3A+PC9kaXY+PC9kaXY+PC9kaXY+PC9k
aXY+PC9kaXY+PC9ib2R5PjwvaHRtbD4=

--_000_62BFE5680C037E4DA0B0A08946C0933DCE425C2Arrsmsx506amrcor_--

From dwl@us.ibm.com  Thu May  6 15:24:20 2010
Return-Path: <dwl@us.ibm.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A17DE3A6A16; Thu,  6 May 2010 15:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.973
X-Spam-Level: 
X-Spam-Status: No, score=-2.973 tagged_above=-999 required=5 tests=[AWL=-0.375, BAYES_00=-2.599, 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 WQXZpRXxuj7w; Thu,  6 May 2010 15:24:16 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by core3.amsl.com (Postfix) with ESMTP id 6FC3F3A688C; Thu,  6 May 2010 15:24:06 -0700 (PDT)
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by e7.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id o46MDimY004919; Thu, 6 May 2010 18:13:44 -0400
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o46MNq5w2093152; Thu, 6 May 2010 18:23:52 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id o46MNqHH031257; Thu, 6 May 2010 18:23:52 -0400
Received: from d01ml605.pok.ibm.com (d01ml605.pok.ibm.com [9.56.227.91]) by d01av01.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVin) with ESMTP id o46MNqH1031251; Thu, 6 May 2010 18:23:52 -0400
In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933DCE425C2A@rrsmsx506.amr.corp.intel.com>
References: <62BFE5680C037E4DA0B0A08946C0933DCE425A2C@rrsmsx506.amr.corp.intel.com>	<z2jb325928b1005061237q9c08d062v25e43996c964839f@mail.gmail.com> <m2xf72742de1005061348h5f0a246doad547c752272fe5@mail.gmail.com> <62BFE5680C037E4DA0B0A08946C0933DCE425C2A@rrsmsx506.amr.corp.intel.com>
To: "Hurliman, John" <john.hurliman@intel.com>
MIME-Version: 1.0
X-KeepSent: B30AB0BD:71074608-8525771B:007AE1F2; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2 HF623 January 16, 2009
Message-ID: <OFB30AB0BD.71074608-ON8525771B.007AE1F2-8525771B.007B06B2@us.ibm.com>
From: David W Levine <dwl@us.ibm.com>
Date: Thu, 6 May 2010 18:23:46 -0400
X-MIMETrack: Serialize by Router on D01ML605/01/M/IBM(Release 8.5.1HF41 | October 22, 2009) at 05/06/2010 18:23:52, Serialize complete at 05/06/2010 18:23:52
Content-Type: multipart/alternative; boundary="=_alternative 007B06AD8525771B_="
Cc: "vwrap@ietf.org" <vwrap@ietf.org>, vwrap-bounces@ietf.org
Subject: Re: [vwrap] ECMA-262 and the Real LLSD type
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 22:24:20 -0000

This is a multipart message in MIME format.
--=_alternative 007B06AD8525771B_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

KzEgb24gSm9zaHVhJ3MgYXBwcm9hY2guIERvY3VtZW50IHRoZSBleHBlY3RlZCBhc1JlYWwgY29l
cmNpb24gYW5kIHlvdXIgDQpiYXNlcyBhcmUgY292ZXJlZCBuaWNlbHkgSSB0aGluay4gDQoNCi0g
RGF2aWQNCn4gWmhhDQoNCg0KDQoNCkZyb206DQoiSHVybGltYW4sIEpvaG4iIDxqb2huLmh1cmxp
bWFuQGludGVsLmNvbT4NClRvOg0KSm9zaHVhIEJlbGwgPGpvc2hAbGluZGVubGFiLmNvbT4sICJ2
d3JhcEBpZXRmLm9yZyIgPHZ3cmFwQGlldGYub3JnPg0KRGF0ZToNCjA1LzA2LzIwMTAgMDQ6NTUg
UE0NClN1YmplY3Q6DQpSZTogW3Z3cmFwXSBFQ01BLTI2MiBhbmQgdGhlIFJlYWwgTExTRCB0eXBl
DQpTZW50IGJ5Og0KdndyYXAtYm91bmNlc0BpZXRmLm9yZw0KDQoNCg0KSeKAmW0gZmluZSB3aXRo
IHRoYXQgYXBwcm9hY2guDQpKb2huDQogDQpGcm9tOiB2d3JhcC1ib3VuY2VzQGlldGYub3JnIFtt
YWlsdG86dndyYXAtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIA0KSm9zaHVhIEJlbGwN
ClNlbnQ6IFRodXJzZGF5LCBNYXkgMDYsIDIwMTAgMTo0OCBQTQ0KVG86IHZ3cmFwQGlldGYub3Jn
DQpTdWJqZWN0OiBSZTogW3Z3cmFwXSBFQ01BLTI2MiBhbmQgdGhlIFJlYWwgTExTRCB0eXBlDQog
DQpJIGRpZCBzb21lIHBsYXlpbmcgaW4gYW4gRUNNQVNjcmlwdCBpbXBsZW1lbnRhdGlvbiBvZiBM
TFNELCBmb2xsb3dpbmcgDQpKb2huJ3Mgc3VnZ2VzdGlvbnMgb2Ygc2VyaWFsaXppbmcgTmFOLCAr
Ly0gSW5maW5pdHksIGFuZCBhbHNvIG5lZ2F0aXZlIA0KemVybywgYXMgc3RyaW5ncyB3aGVuIHNl
cmlhbGl6aW5nIHRvIEpTT04uIFJvdW5kLXRyaXBwaW5nIHdvcmtzIGxpa2UgYSANCmNoYXJtLCBh
c3N1bWluZyBvZiBjb3Vyc2UgdGhhdCB5b3UncmUgdGVzdGluZyB0aGUgcmVzdWx0cyB1c2luZyBh
biANCiJhc1JlYWwiIGNvZXJjaW9uIHRoYXQgZm9sbG93cyB0aGUgc2FtZSBsb2dpYywgd2hpY2gg
YW4gTExTRCANCmltcGxlbWVudGF0aW9uIHNob3VsZCBiZS4NCiANCkNyb2NrZm9yZCdzIGh0dHA6
Ly93d3cuanNvbi5vcmcvanMuaHRtbCBwYWdlIGV2ZW4gaGludHMgYXQgdGhpcyBhcHByb2FjaCAN
CmF0IHRoZSBib3R0b20sIHN1Z2dlc3RpbmcgdGhhdCBub24tZmluaXRlIHZhbHVlcyBjb3VsZCBi
ZSBzZXJpYWxpemVkIHRvIA0KSlNPTiBhcyBzdHJpbmdzLg0KIA0KT24gVGh1LCBNYXkgNiwgMjAx
MCBhdCAxMjozNyBQTSwgTWVhZGhiaCBIYW1yaWNrIDxvaG1lYWRoYmhAZ21haWwuY29tPiANCndy
b3RlOg0Kay4gc28gaSBwaW5nZWQgZG91ZyBjcm9ja2ZvcmQgYWJvdXQgaXQuIGhpcyByZXNwb25z
ZSB3YXMgdGhhdCBKU09ODQp3YW50cyB0byBiZSBpbmRlcGVuZGVudCBvZiBhbnkgZmxvYXRpbmcg
cG9pbnQgc3RhbmRhcmQsIGFuZCB0aHVzIG9ubHkNCnJlcHJlc2VudHMgZmluaXRlIG51bWJlcnMu
DQoNCnNvLi4uIGEpIGl0J3Mgbm90IGEgbWlzdGFrZSBvciBhbiBvdmVyc2lnaHQgdGhhdCB5b3Ug
Y2FuJ3QgcmVwcmVzZW50DQpOYU5zIGFzIEpTT04tTnVtYmVycyBhbmQgYikgZXZlbiBpZiBpdCBz
b21laG93IHdvcmtlZCBpbiBjdXJyZW50DQppbXBsZW1lbnRhdGlvbnMsIGl0J3Mgbm90IHRoZSBp
bnRlbnQgb2YgdGhlIEpTT04gZGVzaWduZXJzLCBzbywgaXQgbWF5DQpub3Qgd29yayBpbiB0aGUg
ZnV0dXJlLg0KDQpzbyBkbyB3ZSBrbm93IGhvdyBpbXBvcnRhbnQgaXQgaXMgdG8gcmVwcmVzZW50
IGVhY2ggb2YgdGhlIGRpc3RpbmN0DQpub24tZmluaXRlIHJlYWxzPw0KDQotY2hlZXJzDQotbWVh
ZGhiaA0KLS0NCm1lYWRoYmggaGFtcmljayAqIGl0J3MgcHJvbm91bmNlZCAibWFldmUiDQpAT2hN
ZWFkaGJoICogaHR0cDovL21lYWRoYmgub3JnLyAqIE9oTWVhZGhiaEBnbWFpbC5jb20NCg0KDQoN
Ck9uIFRodSwgTWF5IDYsIDIwMTAgYXQgMTA6MzYgQU0sIEh1cmxpbWFuLCBKb2huIDxqb2huLmh1
cmxpbWFuQGludGVsLmNvbT4gDQp3cm90ZToNCj4gSW4gZHJhZnQtaGFtcmljay1sbHNkLTAwICIz
LjIuIEpTT04gU2VyaWFsaXphdGlvbiIgaXQgc3RhdGVzOg0KPg0KPiAgIFJlYWwgIExMU0QgJ1Jl
YWwnIHZhbHVlcyBhcmUgcmVwcmVzZW50ZWQgYnkgdGhlIEpTT04gbm9uLXRlcm1pbmFsIA0KJ251
bWJlcicuDQo+DQo+IFRoZW4gbGF0ZXIgaW4gIkFwcGVuZGl4IEEuIEFCTkYgb2YgUmVhbCBWYWx1
ZXMiIGl0IGxpc3RzIGEgc2VyaWVzIG9mIA0Kc3RyaW5ncyB0aGF0IGNhbiBiZSBjb252ZXJ0ZWQg
aW50byByZWFsIHZhbHVlczoNCj4NCj4gICBuZWdhdGl2ZS1pbmZpbml0eSA9ICAleDJELjQ5LjZF
LjY2LjY5LDZFLjY5Ljc0Ljc5ICAgOyAiLUluZmluaXR5Ig0KPiAgIG5lZ2F0aXZlLXplcm8gICAg
ID0gICV4MkQuNUEuNjUuNzIuNkYgICAgICAgICAgICAgICA7ICItWmVybyINCj4gICB6ZXJvICAg
ICAgICAgICAgICA9ICAleDMwLjJFLjMwICAgICAgICAgICAgICAgICAgICAgOyAiMC4wIg0KPiAg
IHBvc2l0aXZlLXplcm8gICAgID0gICV4MkIuNUEuNjUuNzIuNkYgICAgICAgICAgICAgICA7ICIr
WmVybyINCj4gICBwb3NpdGl2ZS1pbmZpbml0eSA9ICAleDJCLjQ5LjZFLjY2LjY5LDZFLjY5Ljc0
Ljc5ICAgOyAiK0luZmluaXR5Ig0KPiAgIHNpZ25hbGluZy1uYW4gICAgICAgPSAgJTRFLjYxLjRF
LjUzICAgICAgICAgICAgICAgICAgIDsgIk5hTlMiDQo+ICAgcXVpZXQtbmFuICAgICAgICAgPSAg
JTRFLjYxLjRFLjUxICAgICAgICAgICAgICAgICAgIDsgIk5hTlEiDQo+DQo+IERvZXMgdGhpcyBt
ZWFuIHRoYXQgYW4gTExTRCByZWFsIHR5cGUgd2l0aCBhIHZhbHVlIG9mIC1JbmZpbml0eSBuZWVk
cyB0byANCmJlIGNvbnZlcnRlZCB0byBhIEpTT04gc3RyaW5nLCBhbmQgd291bGQgYmUgZGVjb2Rl
ZCBvbiB0aGUgcmVjZWl2aW5nIHNpZGUgDQphcyBhbiBMTFNEIHN0cmluZyB3aXRoIHZhbHVlICIt
SW5maW5pdHkiICh0aGF0IGhhcHBlbnMgdG8gaGF2ZSBhIHZhbGlkIA0KY29udmVyc2lvbiB0byBh
biBMTFNEIHJlYWwpPyBFQ01BLTI2MiBkb2VzIG5vdCBzdXBwb3J0IEluZmluaXR5LCBOYU4sIGV0
Yy4gDQpmb3IgdGhlIEpTT04gJ251bWJlcicgdHlwZSBzbyBpdCBsb29rcyBsaWtlIHdlIG5lZWQg
dG8gdHJhbnNtaXQgdGhvc2UgDQp2YWx1ZXMgYXMgc3RyaW5ncy4NCj4NCj4gSm9obg0KPiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiB2d3JhcCBtYWls
aW5nIGxpc3QNCj4gdndyYXBAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby92d3JhcA0KPg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCnZ3cmFwIG1haWxpbmcgbGlzdA0KdndyYXBAaWV0Zi5vcmcNCmh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXANCiBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KdndyYXAgbWFpbGluZyBsaXN0DQp2d3JhcEBp
ZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92d3JhcA0KDQoN
Cg0K
--=_alternative 007B06AD8525771B_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPisxIG9uIEpvc2h1YSdzIGFwcHJv
YWNoLiBEb2N1bWVudCB0aGUNCmV4cGVjdGVkIGFzUmVhbCBjb2VyY2lvbiBhbmQgeW91ciBiYXNl
cyBhcmUgY292ZXJlZCBuaWNlbHkgSSB0aGluay4gPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNp
emU9MiBmYWNlPSJzYW5zLXNlcmlmIj4tIERhdmlkPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBm
YWNlPSJzYW5zLXNlcmlmIj5+IFpoYTwvZm9udD4NCjxicj4NCjxicj4NCjxicj4NCjxicj4NCjx0
YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+PGZvbnQgc2l6ZT0xIGNvbG9y
PSM1ZjVmNWYgZmFjZT0ic2Fucy1zZXJpZiI+RnJvbTo8L2ZvbnQ+DQo8dGQ+PGZvbnQgc2l6ZT0x
IGZhY2U9InNhbnMtc2VyaWYiPiZxdW90O0h1cmxpbWFuLCBKb2huJnF1b3Q7ICZsdDtqb2huLmh1
cmxpbWFuQGludGVsLmNvbSZndDs8L2ZvbnQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD48Zm9udCBz
aXplPTEgY29sb3I9IzVmNWY1ZiBmYWNlPSJzYW5zLXNlcmlmIj5Ubzo8L2ZvbnQ+DQo8dGQ+PGZv
bnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPkpvc2h1YSBCZWxsICZsdDtqb3NoQGxpbmRlbmxh
Yi5jb20mZ3Q7LA0KJnF1b3Q7dndyYXBAaWV0Zi5vcmcmcXVvdDsgJmx0O3Z3cmFwQGlldGYub3Jn
Jmd0OzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPjxmb250IHNpemU9MSBjb2xvcj0jNWY1
ZjVmIGZhY2U9InNhbnMtc2VyaWYiPkRhdGU6PC9mb250Pg0KPHRkPjxmb250IHNpemU9MSBmYWNl
PSJzYW5zLXNlcmlmIj4wNS8wNi8yMDEwIDA0OjU1IFBNPC9mb250Pg0KPHRyIHZhbGlnbj10b3A+
DQo8dGQ+PGZvbnQgc2l6ZT0xIGNvbG9yPSM1ZjVmNWYgZmFjZT0ic2Fucy1zZXJpZiI+U3ViamVj
dDo8L2ZvbnQ+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPlJlOiBbdndyYXBd
IEVDTUEtMjYyIGFuZCB0aGUgUmVhbCBMTFNEDQp0eXBlPC9mb250Pg0KPHRyIHZhbGlnbj10b3A+
DQo8dGQ+PGZvbnQgc2l6ZT0xIGNvbG9yPSM1ZjVmNWYgZmFjZT0ic2Fucy1zZXJpZiI+U2VudCBi
eTo8L2ZvbnQ+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPnZ3cmFwLWJvdW5j
ZXNAaWV0Zi5vcmc8L2ZvbnQ+PC90YWJsZT4NCjxicj4NCjxociBub3NoYWRlPg0KPGJyPg0KPGJy
Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj0jMDA0MDgwIGZhY2U9IkNhbGlicmkiPknigJltIGZp
bmUgd2l0aCB0aGF0IGFwcHJvYWNoLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgY29sb3I9IzAw
NDA4MCBmYWNlPSJDYWxpYnJpIj5Kb2huPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBjb2xvcj0j
MDA0MDgwIGZhY2U9IkNhbGlicmkiPiZuYnNwOzwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFj
ZT0iVGFob21hIj48Yj5Gcm9tOjwvYj4gdndyYXAtYm91bmNlc0BpZXRmLm9yZyBbPC9mb250Pjxh
IGhyZWY9Im1haWx0bzp2d3JhcC1ib3VuY2VzQGlldGYub3JnIj48Zm9udCBzaXplPTIgZmFjZT0i
VGFob21hIj5tYWlsdG86dndyYXAtYm91bmNlc0BpZXRmLm9yZzwvZm9udD48L2E+PGZvbnQgc2l6
ZT0yIGZhY2U9IlRhaG9tYSI+XQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5Kb3NodWEgQmVsbDxiPjxi
cj4NClNlbnQ6PC9iPiBUaHVyc2RheSwgTWF5IDA2LCAyMDEwIDE6NDggUE08Yj48YnI+DQpUbzo8
L2I+IHZ3cmFwQGlldGYub3JnPGI+PGJyPg0KU3ViamVjdDo8L2I+IFJlOiBbdndyYXBdIEVDTUEt
MjYyIGFuZCB0aGUgUmVhbCBMTFNEIHR5cGU8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zIGZhY2U9
IlRpbWVzIE5ldyBSb21hbiI+Jm5ic3A7PC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJU
aW1lcyBOZXcgUm9tYW4iPkkgZGlkIHNvbWUgcGxheWluZyBpbiBhbiBFQ01BU2NyaXB0DQppbXBs
ZW1lbnRhdGlvbiBvZiBMTFNELCBmb2xsb3dpbmcgSm9obidzIHN1Z2dlc3Rpb25zIG9mIHNlcmlh
bGl6aW5nIE5hTiwNCisvLSBJbmZpbml0eSwgYW5kIGFsc28gbmVnYXRpdmUgemVybywgYXMgc3Ry
aW5ncyB3aGVuIHNlcmlhbGl6aW5nIHRvIEpTT04uDQpSb3VuZC10cmlwcGluZyB3b3JrcyBsaWtl
IGEgY2hhcm0sIGFzc3VtaW5nIG9mIGNvdXJzZSB0aGF0IHlvdSdyZSB0ZXN0aW5nDQp0aGUgcmVz
dWx0cyB1c2luZyBhbiAmcXVvdDthc1JlYWwmcXVvdDsgY29lcmNpb24gdGhhdCBmb2xsb3dzIHRo
ZSBzYW1lDQpsb2dpYywgd2hpY2ggYW4gTExTRCBpbXBsZW1lbnRhdGlvbiBzaG91bGQgYmUuPC9m
b250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPiZuYnNwOzwvZm9u
dD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj5Dcm9ja2ZvcmQncyA8
L2ZvbnQ+PGEgaHJlZj1odHRwOi8vd3d3Lmpzb24ub3JnL2pzLmh0bWw+PGZvbnQgc2l6ZT0zIGNv
bG9yPWJsdWUgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48dT5odHRwOi8vd3d3Lmpzb24ub3JnL2pz
Lmh0bWw8L3U+PC9mb250PjwvYT48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj4N
CnBhZ2UgZXZlbiBoaW50cyBhdCB0aGlzIGFwcHJvYWNoIGF0IHRoZSBib3R0b20sIHN1Z2dlc3Rp
bmcgdGhhdCBub24tZmluaXRlDQp2YWx1ZXMgY291bGQgYmUgc2VyaWFsaXplZCB0byBKU09OIGFz
IHN0cmluZ3MuPC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4i
PiZuYnNwOzwvZm9udD4NCjxicj48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj5P
biBUaHUsIE1heSA2LCAyMDEwIGF0IDEyOjM3IFBNLA0KTWVhZGhiaCBIYW1yaWNrICZsdDs8L2Zv
bnQ+PGEgaHJlZj1tYWlsdG86b2htZWFkaGJoQGdtYWlsLmNvbT48Zm9udCBzaXplPTMgY29sb3I9
Ymx1ZSBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjx1Pm9obWVhZGhiaEBnbWFpbC5jb208L3U+PC9m
b250PjwvYT48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj4mZ3Q7DQp3cm90ZTo8
L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+ay4gc28gaSBw
aW5nZWQgZG91ZyBjcm9ja2ZvcmQgYWJvdXQNCml0LiBoaXMgcmVzcG9uc2Ugd2FzIHRoYXQgSlNP
Tjxicj4NCndhbnRzIHRvIGJlIGluZGVwZW5kZW50IG9mIGFueSBmbG9hdGluZyBwb2ludCBzdGFu
ZGFyZCwgYW5kIHRodXMgb25seTxicj4NCnJlcHJlc2VudHMgZmluaXRlIG51bWJlcnMuPGJyPg0K
PGJyPg0Kc28uLi4gYSkgaXQncyBub3QgYSBtaXN0YWtlIG9yIGFuIG92ZXJzaWdodCB0aGF0IHlv
dSBjYW4ndCByZXByZXNlbnQ8YnI+DQpOYU5zIGFzIEpTT04tTnVtYmVycyBhbmQgYikgZXZlbiBp
ZiBpdCBzb21laG93IHdvcmtlZCBpbiBjdXJyZW50PGJyPg0KaW1wbGVtZW50YXRpb25zLCBpdCdz
IG5vdCB0aGUgaW50ZW50IG9mIHRoZSBKU09OIGRlc2lnbmVycywgc28sIGl0IG1heTxicj4NCm5v
dCB3b3JrIGluIHRoZSBmdXR1cmUuPGJyPg0KPGJyPg0Kc28gZG8gd2Uga25vdyBob3cgaW1wb3J0
YW50IGl0IGlzIHRvIHJlcHJlc2VudCBlYWNoIG9mIHRoZSBkaXN0aW5jdDxicj4NCm5vbi1maW5p
dGUgcmVhbHM/PC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJUaW1lcyBOZXcgUm9tYW4i
Pjxicj4NCi1jaGVlcnM8YnI+DQotbWVhZGhiaDxicj4NCi0tPGJyPg0KbWVhZGhiaCBoYW1yaWNr
ICogaXQncyBwcm9ub3VuY2VkICZxdW90O21hZXZlJnF1b3Q7PGJyPg0KQE9oTWVhZGhiaCAqIDwv
Zm9udD48YSBocmVmPWh0dHA6Ly9tZWFkaGJoLm9yZy8gdGFyZ2V0PV9ibGFuaz48Zm9udCBzaXpl
PTMgY29sb3I9Ymx1ZSBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjx1Pmh0dHA6Ly9tZWFkaGJoLm9y
Zy88L3U+PC9mb250PjwvYT48Zm9udCBzaXplPTMgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj4NCiog
PC9mb250PjxhIGhyZWY9bWFpbHRvOk9oTWVhZGhiaEBnbWFpbC5jb20+PGZvbnQgc2l6ZT0zIGNv
bG9yPWJsdWUgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48dT5PaE1lYWRoYmhAZ21haWwuY29tPC91
PjwvZm9udD48L2E+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PGJyPg0KPGJy
Pg0KPGJyPg0KPGJyPg0KT24gVGh1LCBNYXkgNiwgMjAxMCBhdCAxMDozNiBBTSwgSHVybGltYW4s
IEpvaG4gJmx0OzwvZm9udD48YSBocmVmPW1haWx0bzpqb2huLmh1cmxpbWFuQGludGVsLmNvbT48
Zm9udCBzaXplPTMgY29sb3I9Ymx1ZSBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjx1PmpvaG4uaHVy
bGltYW5AaW50ZWwuY29tPC91PjwvZm9udD48L2E+PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5l
dyBSb21hbiI+Jmd0Ow0Kd3JvdGU6PC9mb250Pg0KPGJyPjxmb250IHNpemU9MyBmYWNlPSJUaW1l
cyBOZXcgUm9tYW4iPiZndDsgSW4gZHJhZnQtaGFtcmljay1sbHNkLTAwICZxdW90OzMuMi4NCkpT
T04gU2VyaWFsaXphdGlvbiZxdW90OyBpdCBzdGF0ZXM6PGJyPg0KJmd0Ozxicj4NCiZndDsgJm5i
c3A7IFJlYWwgJm5ic3A7TExTRCAnUmVhbCcgdmFsdWVzIGFyZSByZXByZXNlbnRlZCBieSB0aGUg
SlNPTiBub24tdGVybWluYWwNCidudW1iZXInLjxicj4NCiZndDs8YnI+DQomZ3Q7IFRoZW4gbGF0
ZXIgaW4gJnF1b3Q7QXBwZW5kaXggQS4gQUJORiBvZiBSZWFsIFZhbHVlcyZxdW90OyBpdCBsaXN0
cw0KYSBzZXJpZXMgb2Ygc3RyaW5ncyB0aGF0IGNhbiBiZSBjb252ZXJ0ZWQgaW50byByZWFsIHZh
bHVlczo8YnI+DQomZ3Q7PGJyPg0KJmd0OyAmbmJzcDsgbmVnYXRpdmUtaW5maW5pdHkgPSAmbmJz
cDsleDJELjQ5LjZFLjY2LjY5LDZFLjY5Ljc0Ljc5ICZuYnNwOw0KOyAmcXVvdDstSW5maW5pdHkm
cXVvdDs8YnI+DQomZ3Q7ICZuYnNwOyBuZWdhdGl2ZS16ZXJvICZuYnNwOyAmbmJzcDsgPSAmbmJz
cDsleDJELjVBLjY1LjcyLjZGICZuYnNwOw0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgOyAmcXVvdDstWmVybyZxdW90Ozxicj4NCiZndDsgJm5ic3A7IHplcm8gJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7PSAmbmJzcDsleDMw
LjJFLjMwDQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgOw0KJnF1b3Q7MC4wJnF1b3Q7PGJyPg0KJmd0OyAmbmJzcDsg
cG9zaXRpdmUtemVybyAmbmJzcDsgJm5ic3A7ID0gJm5ic3A7JXgyQi41QS42NS43Mi42RiAmbmJz
cDsNCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IDsgJnF1b3Q7K1pl
cm8mcXVvdDs8YnI+DQomZ3Q7ICZuYnNwOyBwb3NpdGl2ZS1pbmZpbml0eSA9ICZuYnNwOyV4MkIu
NDkuNkUuNjYuNjksNkUuNjkuNzQuNzkgJm5ic3A7DQo7ICZxdW90OytJbmZpbml0eSZxdW90Ozxi
cj4NCiZndDsgJm5ic3A7IHNpZ25hbGluZy1uYW4gJm5ic3A7ICZuYnNwOyAmbmJzcDsgPSAmbmJz
cDslNEUuNjEuNEUuNTMgJm5ic3A7DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7IDsgJnF1b3Q7TmFOUyZxdW90Ozxicj4NCiZndDsgJm5ic3A7
IHF1aWV0LW5hbiAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgPSAmbmJzcDslNEUuNjEuNEUu
NTENCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7IDsgJnF1b3Q7TmFOUSZxdW90Ozxicj4NCiZndDs8YnI+DQomZ3Q7IERvZXMgdGhp
cyBtZWFuIHRoYXQgYW4gTExTRCByZWFsIHR5cGUgd2l0aCBhIHZhbHVlIG9mIC1JbmZpbml0eSBu
ZWVkcw0KdG8gYmUgY29udmVydGVkIHRvIGEgSlNPTiBzdHJpbmcsIGFuZCB3b3VsZCBiZSBkZWNv
ZGVkIG9uIHRoZSByZWNlaXZpbmcNCnNpZGUgYXMgYW4gTExTRCBzdHJpbmcgd2l0aCB2YWx1ZSAm
cXVvdDstSW5maW5pdHkmcXVvdDsgKHRoYXQgaGFwcGVucyB0bw0KaGF2ZSBhIHZhbGlkIGNvbnZl
cnNpb24gdG8gYW4gTExTRCByZWFsKT8gRUNNQS0yNjIgZG9lcyBub3Qgc3VwcG9ydCBJbmZpbml0
eSwNCk5hTiwgZXRjLiBmb3IgdGhlIEpTT04gJ251bWJlcicgdHlwZSBzbyBpdCBsb29rcyBsaWtl
IHdlIG5lZWQgdG8gdHJhbnNtaXQNCnRob3NlIHZhbHVlcyBhcyBzdHJpbmdzLjxicj4NCiZndDs8
YnI+DQomZ3Q7IEpvaG48YnI+DQomZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fPGJyPg0KJmd0OyB2d3JhcCBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7IDwv
Zm9udD48YSBocmVmPW1haWx0bzp2d3JhcEBpZXRmLm9yZz48Zm9udCBzaXplPTMgY29sb3I9Ymx1
ZSBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjx1PnZ3cmFwQGlldGYub3JnPC91PjwvZm9udD48L2E+
PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PGJyPg0KJmd0OyA8L2ZvbnQ+PGEg
aHJlZj1odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Z3cmFwIHRhcmdldD1f
Ymxhbms+PGZvbnQgc2l6ZT0zIGNvbG9yPWJsdWUgZmFjZT0iVGltZXMgTmV3IFJvbWFuIj48dT5o
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Z3cmFwPC91PjwvZm9udD48L2E+
PGZvbnQgc2l6ZT0zIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PGJyPg0KJmd0Ozxicj4NCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KdndyYXAgbWFp
bGluZyBsaXN0PC9mb250Pjxmb250IHNpemU9MyBjb2xvcj1ibHVlIGZhY2U9IlRpbWVzIE5ldyBS
b21hbiI+PHU+PGJyPg0KPC91PjwvZm9udD48YSBocmVmPW1haWx0bzp2d3JhcEBpZXRmLm9yZz48
Zm9udCBzaXplPTMgY29sb3I9Ymx1ZSBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iPjx1PnZ3cmFwQGll
dGYub3JnPC91PjwvZm9udD48L2E+PGZvbnQgc2l6ZT0zIGNvbG9yPWJsdWUgZmFjZT0iVGltZXMg
TmV3IFJvbWFuIj48dT48YnI+DQo8L3U+PC9mb250PjxhIGhyZWY9aHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby92d3JhcCB0YXJnZXQ9X2JsYW5rPjxmb250IHNpemU9MyBjb2xv
cj1ibHVlIGZhY2U9IlRpbWVzIE5ldyBSb21hbiI+PHU+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby92d3JhcDwvdT48L2ZvbnQ+PC9hPg0KPGJyPjxmb250IHNpemU9MyBmYWNl
PSJUaW1lcyBOZXcgUm9tYW4iPiZuYnNwOzwvZm9udD48dHQ+PGZvbnQgc2l6ZT0yPl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KdndyYXAgbWFpbGlu
ZyBsaXN0PGJyPg0KdndyYXBAaWV0Zi5vcmc8YnI+DQo8L2ZvbnQ+PC90dD48YSBocmVmPWh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXA+PHR0Pjxmb250IHNpemU9Mj5o
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Z3cmFwPC9mb250PjwvdHQ+PC9h
Pjx0dD48Zm9udCBzaXplPTI+PGJyPg0KPC9mb250PjwvdHQ+DQo8YnI+DQo8YnI+DQo=
--=_alternative 007B06AD8525771B_=--

From morgaine.dinova@googlemail.com  Fri May 14 04:32:49 2010
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 855753A69B2 for <vwrap@core3.amsl.com>; Fri, 14 May 2010 04:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.745
X-Spam-Level: *
X-Spam-Status: No, score=1.745 tagged_above=-999 required=5 tests=[AWL=-0.878,  BAYES_80=2, 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 J+wY1ur3DfoR for <vwrap@core3.amsl.com>; Fri, 14 May 2010 04:32:48 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 03A8A3A698C for <vwrap@ietf.org>; Fri, 14 May 2010 04:32:44 -0700 (PDT)
Received: by wyb42 with SMTP id 42so807073wyb.31 for <vwrap@ietf.org>; Fri, 14 May 2010 04:32:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=N1tdVCAN4usmSo1MIUty5CVT1hfnG/98pGBOQjp07rM=; b=eXAeVO2tTWUGeOOLDYmpckdaSYOMLdn62+gVoZsgjN0pmTe1C0bPxfRD9ha5DhTsPH b/7QaKczWBymdpqbp8QcazVuiTqv17r+Bmu/KsIyOZaU1T5ufhJKJvR553Dt0vRqZExg RLbfxVCooWA9Pe9tsPOMqxC/uQrdu0I8gOBMY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=XEXZG/3/SlJKnpAMOVbSXQvwarP0GgtHhzrY7YJdGkV2hBmqzJGHLt3x2H6gHpwnIz 4adTx7ps5WHY8+ViDWqD0mcpnOi/rdIqTRM8ynM7eH1AT3YQ1sUcR7JvwIhNtZcBJZS8 0/TpKCm6myRUz+H0L826vUSSp23eKp8rPGvxg=
MIME-Version: 1.0
Received: by 10.227.72.145 with SMTP id m17mr1089337wbj.164.1273836752381;  Fri, 14 May 2010 04:32:32 -0700 (PDT)
Received: by 10.216.26.132 with HTTP; Fri, 14 May 2010 04:32:32 -0700 (PDT)
Date: Fri, 14 May 2010 12:32:32 +0100
Message-ID: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary=0016368332e020a80304868c3bbb
Subject: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2010 11:32:49 -0000

--0016368332e020a80304868c3bbb
Content-Type: text/plain; charset=ISO-8859-1

Despite exceedingly low takeup of IPv6 so far, it's coming, and in the
context of IETF WG rates of progress, it is really imminent.  Of special
relevance to us is that IPv4 addresses are projected to run out within
roughly the same time frame as VWRAP materializes.

There is little point in creating a new VW protocol today purely in the
context of IPv4 without thinking about tomorrow's IPv6 environment.  By the
time that VWRAP is fully defined, we should expect a substantial and rapidly
increasing proportion of VWRAP implementations to occur in IPv6-accessible
worlds.  This is a situation for which we need to plan now, otherwise the
protocol will be obsolete before it's even ready.

To get the ball rolling, here are a few IPv6-related issues that we could
usefully address in the group:


   - The 128-bit IP address of IPv6 is likely to become a common payload, so
   it should be supported natively.  LLSD already supports one 128-bit data
   type of course, the UUID.  IPv6 addresses should not be transported in UUID
   fields however, since their statistical properties and semantics are totally
   different.  In any case, the two spaces are disjoint so confusing them would
   be a mistake.  The IPv6 address seems a good candidate for its own defined
   type, in the absence of wide integers.


   - The extremely large address space of IPv6 has often been portrayed as
   allowing everything around us to have its own IP address.  In the context of
   virtual worlds, this idea can actually be put to good use, with each virtual
   object bearing its own IPv6 address.  One candidate application for this has
   already been described in earlier discussions --- for example, implementing
   virtual object simulation in two parts, one client-side and one world-side,
   the two parts communicating directly.  IPv6 addressing of objects makes this
   relatively easy to achieve efficiently, so its implementation in IPv6-based
   worlds is almost inevitable before long.  VWRAP should be ready for this.


   - The event queue in current implementations provides an indirect and
   highly inefficient way of achieving world-to-client communications.  IPv6
   offers opportunities for direct communication that can make the event queue
   approach obsolete, so it's worth examining IPv6-oriented alternatives.


   - We recently discussed feature and protocol negotiation within VWRAP.
   IPv6 provides much opportunity for new features and protocol pathways to be
   negotiated between endpoints, so it gives us a very real and imminent set of
   use cases for negotiation.


It would also be a feather in VWRAP's cap to be considered an "IPv6-capable
application protocol" in a stronger sense than just to be carried by IPv6
networks.  IPv6 does after all bring new abilities to the table, such as the
huge addressing, and it would be a mistake to ignore them.


Morgaine.

--0016368332e020a80304868c3bbb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Despite exceedingly low takeup of IPv6 so far, it&#39;s coming, and in the =
context of IETF WG rates of progress, it is really imminent.=A0 Of special =
relevance to us is that IPv4 addresses are projected to run out within roug=
hly the same time frame as VWRAP materializes.<br>
<br>There is little point in creating a new VW protocol today purely in the=
 context of IPv4 without thinking about tomorrow&#39;s IPv6 environment.=A0=
 By the time that VWRAP is fully defined, we should expect a substantial an=
d rapidly increasing proportion of VWRAP implementations to occur in IPv6-a=
ccessible worlds.=A0 This is a situation for which we need to plan now, oth=
erwise the protocol will be obsolete before it&#39;s even ready.<br>
<br>To get the ball rolling, here are a few IPv6-related issues that we cou=
ld usefully address in the group:<br><br><ul><li>The 128-bit IP address of =
IPv6 is likely to become a common payload, so it should be supported native=
ly.=A0 LLSD already supports one 128-bit data type of course, the UUID.=A0 =
IPv6 addresses should not be transported in UUID fields however, since thei=
r statistical properties and semantics are totally different.=A0 In any cas=
e, the two spaces are disjoint so confusing them would be a mistake.=A0 The=
 IPv6 address seems a good candidate for its own defined type, in the absen=
ce of wide integers.<br>
</li></ul><ul><li>The extremely large address space of IPv6 has often been =
portrayed as allowing everything around us to have its own IP address.=A0 I=
n the context of virtual worlds, this idea can actually be put to good use,=
 with each virtual object bearing its own IPv6 address.=A0 One candidate ap=
plication for this has already been described in earlier discussions --- fo=
r example, implementing virtual object simulation in two parts, one client-=
side and one world-side, the two parts communicating directly.=A0 IPv6 addr=
essing of objects makes this relatively easy to achieve efficiently, so its=
 implementation in IPv6-based worlds is almost inevitable before long.=A0 V=
WRAP should be ready for this.</li>
</ul><ul><li>The event queue in current implementations provides an indirec=
t and highly inefficient way of achieving world-to-client communications.=
=A0 IPv6 offers opportunities for direct communication that can make the ev=
ent queue approach obsolete, so it&#39;s worth examining IPv6-oriented alte=
rnatives.</li>
</ul><ul><li>We recently discussed feature and protocol negotiation within =
VWRAP.=A0 IPv6 provides much opportunity for new features and protocol path=
ways to be negotiated between endpoints, so it gives us a very real and imm=
inent set of use cases for negotiation.<br>
</li></ul><br>It would also be a feather in VWRAP&#39;s cap to be considere=
d an &quot;IPv6-capable application protocol&quot; in a stronger sense than=
 just to be carried by IPv6 networks.=A0 IPv6 does after all bring new abil=
ities to the table, such as the huge addressing, and it would be a mistake =
to ignore them.<br>
<br><br>Morgaine.<br><br><br><br>

--0016368332e020a80304868c3bbb--

From dzonatas@gmail.com  Fri May 14 08:42:13 2010
Return-Path: <dzonatas@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 39CC33A68DF for <vwrap@core3.amsl.com>; Fri, 14 May 2010 08:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.695
X-Spam-Level: ****
X-Spam-Status: No, score=4.695 tagged_above=-999 required=5 tests=[AWL=4.694,  BAYES_50=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 JkGNPFGumMuy for <vwrap@core3.amsl.com>; Fri, 14 May 2010 08:42:12 -0700 (PDT)
Received: from mail-pz0-f187.google.com (mail-pz0-f187.google.com [209.85.222.187]) by core3.amsl.com (Postfix) with ESMTP id 44EE73A6882 for <vwrap@ietf.org>; Fri, 14 May 2010 08:42:12 -0700 (PDT)
Received: by pzk17 with SMTP id 17so1270869pzk.5 for <vwrap@ietf.org>; Fri, 14 May 2010 08:42:00 -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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=wqmZ95VF2esaUd3WGaa5hTtbQt2gmz8wJ5ENChVHvNI=; b=qnyc9NmOkb94/9K+kZhwgd8+exPMqEysKTUuoCKxvfEjyHL2WBKxiDowCw38QKVzyZ 8D+bugtby6Ou/klkv5wbRkdex+HgMHQhfs6B2NNxk3Z7lKA56wQ9rOK8vnnTtYRwyB6Y QIGKjzrWfb4EBMm5l1lOxfP9m73EGNPdeNnZc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=aLrnAt4anFm5DugvUMbpHkiGSXZ5kkrSAEDOtXyFIz9fhtcai+NZVsTjuTifvAsH7i utTP7BVLkYQfhN35xIrD0HPI2rZGlEwh+Y1Gut5GjxF7m8Vdm38cqFG5pzMFvxOGPt9V SU277Q/p7vRy9mcEuTBQahspaA59jFHBw1E8U=
Received: by 10.114.237.24 with SMTP id k24mr1294245wah.29.1273851719828; Fri, 14 May 2010 08:41:59 -0700 (PDT)
Received: from [192.168.0.50] (adsl-64-160-119-85.dsl.scrm01.pacbell.net [64.160.119.85]) by mx.google.com with ESMTPS id b6sm20967746wam.9.2010.05.14.08.41.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 14 May 2010 08:41:58 -0700 (PDT)
Message-ID: <4BED72D9.8030502@gmail.com>
Date: Fri, 14 May 2010 08:57:13 -0700
From: Dzonatas Sol <dzonatas@gmail.com>
User-Agent: Mozilla-Thunderbird 2.0.0.24 (X11/20100329)
MIME-Version: 1.0
To: Morgaine <morgaine.dinova@googlemail.com>
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com>
In-Reply-To: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: vwrap@ietf.org
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2010 15:42:13 -0000

There has been discussion about IPv6 with LLP, and that's probably only 
where any extra type is needed. In any other format or scheme there is 
no need for an extra type since a string value can cover the colon-dot 
notation of IPv6.

A UUID used in the IPv6 address is not really a UUID even if it can be 
used the same way. The exception being that unique generated IDs would 
need to check to make sure they don't collide with predefined addresses. 
The real benefit for this method is better left behind a custom network 
that isn't directly bridged to the Internet. There would need to be a 
gateway to convert UUID-IPv6 values to valid Internet addresses. The 
special network most likely would use the multi-cast broadcast features 
of IPv6. Without much detailed digression, newer technology for 
multi-core CPUs have broadcast arrays that would make the IPv6 
multi-cast probably not needed anymore for such solutions.

Morgaine wrote:
> Despite exceedingly low takeup of IPv6 so far, it's coming, and in the 
> context of IETF WG rates of progress, it is really imminent.� Of 
> special relevance to us is that IPv4 addresses are projected to run 
> out within roughly the same time frame as VWRAP materializes.
>
> There is little point in creating a new VW protocol today purely in 
> the context of IPv4 without thinking about tomorrow's IPv6 
> environment.� By the time that VWRAP is fully defined, we should 
> expect a substantial and rapidly increasing proportion of VWRAP 
> implementations to occur in IPv6-accessible worlds.� This is a 
> situation for which we need to plan now, otherwise the protocol will 
> be obsolete before it's even ready.
>
> To get the ball rolling, here are a few IPv6-related issues that we 
> could usefully address in the group:
>
>     * The 128-bit IP address of IPv6 is likely to become a common
>       payload, so it should be supported natively.� LLSD already
>       supports one 128-bit data type of course, the UUID.� IPv6
>       addresses should not be transported in UUID fields however,
>       since their statistical properties and semantics are totally
>       different.� In any case, the two spaces are disjoint so
>       confusing them would be a mistake.� The IPv6 address seems a
>       good candidate for its own defined type, in the absence of wide
>       integers.
>
>     * The extremely large address space of IPv6 has often been
>       portrayed as allowing everything around us to have its own IP
>       address.� In the context of virtual worlds, this idea can
>       actually be put to good use, with each virtual object bearing
>       its own IPv6 address.� One candidate application for this has
>       already been described in earlier discussions --- for example,
>       implementing virtual object simulation in two parts, one
>       client-side and one world-side, the two parts communicating
>       directly.� IPv6 addressing of objects makes this relatively easy
>       to achieve efficiently, so its implementation in IPv6-based
>       worlds is almost inevitable before long.� VWRAP should be ready
>       for this.
>
>     * The event queue in current implementations provides an indirect
>       and highly inefficient way of achieving world-to-client
>       communications.� IPv6 offers opportunities for direct
>       communication that can make the event queue approach obsolete,
>       so it's worth examining IPv6-oriented alternatives.
>
>     * We recently discussed feature and protocol negotiation within
>       VWRAP.� IPv6 provides much opportunity for new features and
>       protocol pathways to be negotiated between endpoints, so it
>       gives us a very real and imminent set of use cases for negotiation.
>
>
> It would also be a feather in VWRAP's cap to be considered an 
> "IPv6-capable application protocol" in a stronger sense than just to 
> be carried by IPv6 networks.� IPv6 does after all bring new abilities 
> to the table, such as the huge addressing, and it would be a mistake 
> to ignore them.
>
>
> Morgaine.
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>   


From rbarnes@bbn.com  Mon May 17 07:08:39 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB7E93A6883 for <vwrap@core3.amsl.com>; Mon, 17 May 2010 07:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.008
X-Spam-Level: 
X-Spam-Status: No, score=-1.008 tagged_above=-999 required=5 tests=[AWL=-1.009, BAYES_50=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 XORvaDu2LKa1 for <vwrap@core3.amsl.com>; Mon, 17 May 2010 07:08:35 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 5DCBA3A68CB for <vwrap@ietf.org>; Mon, 17 May 2010 07:08:35 -0700 (PDT)
Received: from [192.1.255.188] (port=50119 helo=col-dhcp-192-1-255-188.bbn.com) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OE0za-000Izs-Nr; Mon, 17 May 2010 10:08:26 -0400
Message-Id: <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com>
From: Richard Barnes <rbarnes@bbn.com>
To: Morgaine <morgaine.dinova@googlemail.com>
In-Reply-To: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 17 May 2010 10:08:26 -0400
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: vwrap@ietf.org
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2010 14:08:39 -0000

In the spirit of good layering, it seems like we should be talking =20
about avoiding direct reliance on IP addresses instead of how we can =20
accommodate different addresses in the protocol.  Why is there ever a =20=

need to carry an IP address in this application-layer protocol, as =20
opposed to, say, a DNS name or a URI?

--Richard



On May 14, 2010, at 7:32 AM, Morgaine wrote:

> Despite exceedingly low takeup of IPv6 so far, it's coming, and in =20
> the context of IETF WG rates of progress, it is really imminent.  Of =20=

> special relevance to us is that IPv4 addresses are projected to run =20=

> out within roughly the same time frame as VWRAP materializes.
>
> There is little point in creating a new VW protocol today purely in =20=

> the context of IPv4 without thinking about tomorrow's IPv6 =20
> environment.  By the time that VWRAP is fully defined, we should =20
> expect a substantial and rapidly increasing proportion of VWRAP =20
> implementations to occur in IPv6-accessible worlds.  This is a =20
> situation for which we need to plan now, otherwise the protocol will =20=

> be obsolete before it's even ready.
>
> To get the ball rolling, here are a few IPv6-related issues that we =20=

> could usefully address in the group:
>
> 	=95 The 128-bit IP address of IPv6 is likely to become a common =20=

> payload, so it should be supported natively.  LLSD already supports =20=

> one 128-bit data type of course, the UUID.  IPv6 addresses should =20
> not be transported in UUID fields however, since their statistical =20
> properties and semantics are totally different.  In any case, the =20
> two spaces are disjoint so confusing them would be a mistake.  The =20
> IPv6 address seems a good candidate for its own defined type, in the =20=

> absence of wide integers.
> 	=95 The extremely large address space of IPv6 has often been =20
> portrayed as allowing everything around us to have its own IP =20
> address.  In the context of virtual worlds, this idea can actually =20
> be put to good use, with each virtual object bearing its own IPv6 =20
> address.  One candidate application for this has already been =20
> described in earlier discussions --- for example, implementing =20
> virtual object simulation in two parts, one client-side and one =20
> world-side, the two parts communicating directly.  IPv6 addressing =20
> of objects makes this relatively easy to achieve efficiently, so its =20=

> implementation in IPv6-based worlds is almost inevitable before =20
> long.  VWRAP should be ready for this.
> 	=95 The event queue in current implementations provides an =
indirect =20
> and highly inefficient way of achieving world-to-client =20
> communications.  IPv6 offers opportunities for direct communication =20=

> that can make the event queue approach obsolete, so it's worth =20
> examining IPv6-oriented alternatives.
> 	=95 We recently discussed feature and protocol negotiation =
within =20
> VWRAP.  IPv6 provides much opportunity for new features and protocol =20=

> pathways to be negotiated between endpoints, so it gives us a very =20
> real and imminent set of use cases for negotiation.
>
> It would also be a feather in VWRAP's cap to be considered an "IPv6-=20=

> capable application protocol" in a stronger sense than just to be =20
> carried by IPv6 networks.  IPv6 does after all bring new abilities =20
> to the table, such as the huge addressing, and it would be a mistake =20=

> to ignore them.
>
>
> Morgaine.
>
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap


From dwl@us.ibm.com  Mon May 17 07:51:38 2010
Return-Path: <dwl@us.ibm.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53BC73A6A47; Mon, 17 May 2010 07:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.598
X-Spam-Level: 
X-Spam-Status: No, score=-1.598 tagged_above=-999 required=5 tests=[AWL=-1.600, BAYES_50=0.001, 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 JWxnq4+0v2N0; Mon, 17 May 2010 07:51:37 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by core3.amsl.com (Postfix) with ESMTP id B19783A6A65; Mon, 17 May 2010 07:51:05 -0700 (PDT)
Received: from d01relay05.pok.ibm.com (d01relay05.pok.ibm.com [9.56.227.237]) by e7.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id o4HEeJCs025816; Mon, 17 May 2010 10:40:19 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o4HEooeD081380; Mon, 17 May 2010 10:50:50 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id o4HEoouf028604; Mon, 17 May 2010 11:50:50 -0300
Received: from d01ml605.pok.ibm.com (d01ml605.pok.ibm.com [9.56.227.91]) by d01av02.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVin) with ESMTP id o4HEoob7028587; Mon, 17 May 2010 11:50:50 -0300
In-Reply-To: <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com>
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com>
To: Richard Barnes <rbarnes@bbn.com>
MIME-Version: 1.0
X-KeepSent: C2E23B0D:5B99CD05-85257726:0050CDA0; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2 HF623 January 16, 2009
Message-ID: <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com>
From: David W Levine <dwl@us.ibm.com>
Date: Mon, 17 May 2010 10:50:49 -0400
X-MIMETrack: Serialize by Router on D01ML605/01/M/IBM(Release 8.5.1HF41 | October 22, 2009) at 05/17/2010 10:50:49, Serialize complete at 05/17/2010 10:50:49
Content-Type: multipart/alternative; boundary="=_alternative 00518F0D85257726_="
Cc: vwrap@ietf.org, vwrap-bounces@ietf.org
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2010 14:51:38 -0000

This is a multipart message in MIME format.
--=_alternative 00518F0D85257726_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

dndyYXAtYm91bmNlc0BpZXRmLm9yZyB3cm90ZSBvbiAwNS8xNy8yMDEwIDEwOjA4OjI2IEFNOg0K
DQo+IFtpbWFnZSByZW1vdmVkXSANCj4gDQo+IFJlOiBbdndyYXBdIFZXUkFQIGFuZCBJUHY2DQo+
IA0KPiBSaWNoYXJkIEJhcm5lcyANCj4gDQo+IHRvOg0KPiANCj4gTW9yZ2FpbmUNCj4gDQo+IDA1
LzE3LzIwMTAgMTA6MDkgQU0NCj4gDQo+IFNlbnQgYnk6DQo+IA0KPiB2d3JhcC1ib3VuY2VzQGll
dGYub3JnDQo+IA0KPiBDYzoNCj4gDQo+IHZ3cmFwDQo+IA0KPiBJbiB0aGUgc3Bpcml0IG9mIGdv
b2QgbGF5ZXJpbmcsIGl0IHNlZW1zIGxpa2Ugd2Ugc2hvdWxkIGJlIHRhbGtpbmcgDQo+IGFib3V0
IGF2b2lkaW5nIGRpcmVjdCByZWxpYW5jZSBvbiBJUCBhZGRyZXNzZXMgaW5zdGVhZCBvZiBob3cg
d2UgY2FuIA0KPiBhY2NvbW1vZGF0ZSBkaWZmZXJlbnQgYWRkcmVzc2VzIGluIHRoZSBwcm90b2Nv
bC4gIFdoeSBpcyB0aGVyZSBldmVyIGEgDQo+IG5lZWQgdG8gY2FycnkgYW4gSVAgYWRkcmVzcyBp
biB0aGlzIGFwcGxpY2F0aW9uLWxheWVyIHByb3RvY29sLCBhcyANCj4gb3Bwb3NlZCB0bywgc2F5
LCBhIEROUyBuYW1lIG9yIGEgVVJJPw0KPiANCj4gLS1SaWNoYXJkDQo+IA0KKzEgDQoNCldlIG1h
eSBmcm9tIHRpbWUgdG8gdGltZSBoYXZlIGEgSVAgYWRkcmVzcyBzdHVjayBpbiB0aGUgZm9ybSBv
ZiBhIFVSSQ0Kd2hpY2ggaGFzIHRoZSBkb3R0ZWQgZGVjaW1hbCBmb3JtIG9mIGFuIHJlc291cmNl
LiBUaGUgc3BlYyBzaG91bGQgbWFrZQ0Kc3VyZSB0aGF0IGZvcm0gY2FuIGJlIGFuIElQVjYgYWRk
cmVzcywgYnV0IHRoYXQgc2hvdWxkIGJlIHZlcnkgc3RyYWlnaHQgDQpmb3J3YXJkLiANCg0KVGhl
cmUgbWF5IGJlIHNvbWUgSVBWNiBmZWF0dXJlcyB3aGljaCBldmVudHVhbGx5IGltcGFjdCB1cyBh
dCB0aGUgcHJvdG9jb2wNCmRlc2lnbiBsZXZlbCwgYnV0IHRoZSBlbnRpcmUgVldSQVAgc3BlY2lm
aWNhdGlvbiBoYXMgYmVlbiB3cml0dGVuIGluIHRlcm1zIA0Kb2YNClVSSXMgYW5kIENhcGFiaWxp
dGllcywgbm90IGluIHRlcm1zIG9mIGxvdyBsZXZlbCBJUCBhZGRyZXNzZXMuIEl0IHdvdWxkIA0K
dGFrZSBhbg0KaW5jcmVkaWJseSBwb3dlcmZ1bCBhcmd1bWVudCB0byBzdWdnZXN0IHRoYXQgdGhp
cyBzaG91bGQgY2hhbmdlLiBMaWtld2lzZSwgDQp3aGlsZQ0KSVBWNiBjaGFuZ2VzIGFkZHJlc3Np
bmcgYXQgdGhlIGJvdHRvbSBvZiB0aGUgc3RhY2ssIGl0IGRvZXNuJ3QgYXBwcmVjaWFibHkgDQpj
aGFuZ2UNCnRoZSBjb3N0IG9mIGhvbGRpbmcgb3BlbiBzZXNzaW9ucywgb2YgbWFuYWdpbmcgc29j
a2V0cyBhbmQgYnVmZmVycyBpbnNpZGUgDQpvZg0KY2xpZW50cyAoZXNwZWNpYWxseSBsaWdodHdl
aWdodCBkZXZpY2VzKSBGdXJ0aGVyIHdoaWxlIHdlIGNhbiBhbGwgZGV2b3V0bHkgDQpob3BlDQp0
aGF0IElQVjYgZmluYWxseSBkZXBsb3lzIGJyb2FkbHksIG1ha2luZyBpdCBhIGRlcGVuZGFuY3kg
aW4gdGhlIG5lYXIgdGVybSANCmZlZWxzDQpyYXRoZXIgbGlrZSBhIHJvYWRibG9jayB0byBwb3Nz
aWJsZSBhZG9wdGlvbi4NCg0KLSBEYXZpZA0KfiBaaGENCg0KDQoNCj4gDQo+IE9uIE1heSAxNCwg
MjAxMCwgYXQgNzozMiBBTSwgTW9yZ2FpbmUgd3JvdGU6DQo+IA0KPiA+IERlc3BpdGUgZXhjZWVk
aW5nbHkgbG93IHRha2V1cCBvZiBJUHY2IHNvIGZhciwgaXQncyBjb21pbmcsIGFuZCBpbiANCj4g
PiB0aGUgY29udGV4dCBvZiBJRVRGIFdHIHJhdGVzIG9mIHByb2dyZXNzLCBpdCBpcyByZWFsbHkg
aW1taW5lbnQuICBPZiANCj4gPiBzcGVjaWFsIHJlbGV2YW5jZSB0byB1cyBpcyB0aGF0IElQdjQg
YWRkcmVzc2VzIGFyZSBwcm9qZWN0ZWQgdG8gcnVuIA0KPiA+IG91dCB3aXRoaW4gcm91Z2hseSB0
aGUgc2FtZSB0aW1lIGZyYW1lIGFzIFZXUkFQIG1hdGVyaWFsaXplcy4NCj4gPg0KPiA+IFRoZXJl
IGlzIGxpdHRsZSBwb2ludCBpbiBjcmVhdGluZyBhIG5ldyBWVyBwcm90b2NvbCB0b2RheSBwdXJl
bHkgaW4gDQo+ID4gdGhlIGNvbnRleHQgb2YgSVB2NCB3aXRob3V0IHRoaW5raW5nIGFib3V0IHRv
bW9ycm93J3MgSVB2NiANCj4gPiBlbnZpcm9ubWVudC4gIEJ5IHRoZSB0aW1lIHRoYXQgVldSQVAg
aXMgZnVsbHkgZGVmaW5lZCwgd2Ugc2hvdWxkIA0KPiA+IGV4cGVjdCBhIHN1YnN0YW50aWFsIGFu
ZCByYXBpZGx5IGluY3JlYXNpbmcgcHJvcG9ydGlvbiBvZiBWV1JBUCANCj4gPiBpbXBsZW1lbnRh
dGlvbnMgdG8gb2NjdXIgaW4gSVB2Ni1hY2Nlc3NpYmxlIHdvcmxkcy4gIFRoaXMgaXMgYSANCj4g
PiBzaXR1YXRpb24gZm9yIHdoaWNoIHdlIG5lZWQgdG8gcGxhbiBub3csIG90aGVyd2lzZSB0aGUg
cHJvdG9jb2wgd2lsbCANCj4gPiBiZSBvYnNvbGV0ZSBiZWZvcmUgaXQncyBldmVuIHJlYWR5Lg0K
PiA+DQo+ID4gVG8gZ2V0IHRoZSBiYWxsIHJvbGxpbmcsIGhlcmUgYXJlIGEgZmV3IElQdjYtcmVs
YXRlZCBpc3N1ZXMgdGhhdCB3ZSANCj4gPiBjb3VsZCB1c2VmdWxseSBhZGRyZXNzIGluIHRoZSBn
cm91cDoNCj4gPg0KPiA+ICAgIOKAoiBUaGUgMTI4LWJpdCBJUCBhZGRyZXNzIG9mIElQdjYgaXMg
bGlrZWx5IHRvIGJlY29tZSBhIGNvbW1vbiANCj4gPiBwYXlsb2FkLCBzbyBpdCBzaG91bGQgYmUg
c3VwcG9ydGVkIG5hdGl2ZWx5LiAgTExTRCBhbHJlYWR5IHN1cHBvcnRzIA0KPiA+IG9uZSAxMjgt
Yml0IGRhdGEgdHlwZSBvZiBjb3Vyc2UsIHRoZSBVVUlELiAgSVB2NiBhZGRyZXNzZXMgc2hvdWxk
IA0KPiA+IG5vdCBiZSB0cmFuc3BvcnRlZCBpbiBVVUlEIGZpZWxkcyBob3dldmVyLCBzaW5jZSB0
aGVpciBzdGF0aXN0aWNhbCANCj4gPiBwcm9wZXJ0aWVzIGFuZCBzZW1hbnRpY3MgYXJlIHRvdGFs
bHkgZGlmZmVyZW50LiAgSW4gYW55IGNhc2UsIHRoZSANCj4gPiB0d28gc3BhY2VzIGFyZSBkaXNq
b2ludCBzbyBjb25mdXNpbmcgdGhlbSB3b3VsZCBiZSBhIG1pc3Rha2UuICBUaGUgDQo+ID4gSVB2
NiBhZGRyZXNzIHNlZW1zIGEgZ29vZCBjYW5kaWRhdGUgZm9yIGl0cyBvd24gZGVmaW5lZCB0eXBl
LCBpbiB0aGUgDQo+ID4gYWJzZW5jZSBvZiB3aWRlIGludGVnZXJzLg0KPiA+ICAgIOKAoiBUaGUg
ZXh0cmVtZWx5IGxhcmdlIGFkZHJlc3Mgc3BhY2Ugb2YgSVB2NiBoYXMgb2Z0ZW4gYmVlbiANCj4g
PiBwb3J0cmF5ZWQgYXMgYWxsb3dpbmcgZXZlcnl0aGluZyBhcm91bmQgdXMgdG8gaGF2ZSBpdHMg
b3duIElQIA0KPiA+IGFkZHJlc3MuICBJbiB0aGUgY29udGV4dCBvZiB2aXJ0dWFsIHdvcmxkcywg
dGhpcyBpZGVhIGNhbiBhY3R1YWxseSANCj4gPiBiZSBwdXQgdG8gZ29vZCB1c2UsIHdpdGggZWFj
aCB2aXJ0dWFsIG9iamVjdCBiZWFyaW5nIGl0cyBvd24gSVB2NiANCj4gPiBhZGRyZXNzLiAgT25l
IGNhbmRpZGF0ZSBhcHBsaWNhdGlvbiBmb3IgdGhpcyBoYXMgYWxyZWFkeSBiZWVuIA0KPiA+IGRl
c2NyaWJlZCBpbiBlYXJsaWVyIGRpc2N1c3Npb25zIC0tLSBmb3IgZXhhbXBsZSwgaW1wbGVtZW50
aW5nIA0KPiA+IHZpcnR1YWwgb2JqZWN0IHNpbXVsYXRpb24gaW4gdHdvIHBhcnRzLCBvbmUgY2xp
ZW50LXNpZGUgYW5kIG9uZSANCj4gPiB3b3JsZC1zaWRlLCB0aGUgdHdvIHBhcnRzIGNvbW11bmlj
YXRpbmcgZGlyZWN0bHkuICBJUHY2IGFkZHJlc3NpbmcgDQo+ID4gb2Ygb2JqZWN0cyBtYWtlcyB0
aGlzIHJlbGF0aXZlbHkgZWFzeSB0byBhY2hpZXZlIGVmZmljaWVudGx5LCBzbyBpdHMgDQo+ID4g
aW1wbGVtZW50YXRpb24gaW4gSVB2Ni1iYXNlZCB3b3JsZHMgaXMgYWxtb3N0IGluZXZpdGFibGUg
YmVmb3JlIA0KPiA+IGxvbmcuICBWV1JBUCBzaG91bGQgYmUgcmVhZHkgZm9yIHRoaXMuDQo+ID4g
ICAg4oCiIFRoZSBldmVudCBxdWV1ZSBpbiBjdXJyZW50IGltcGxlbWVudGF0aW9ucyBwcm92aWRl
cyBhbiBpbmRpcmVjdCANCj4gPiBhbmQgaGlnaGx5IGluZWZmaWNpZW50IHdheSBvZiBhY2hpZXZp
bmcgd29ybGQtdG8tY2xpZW50IA0KPiA+IGNvbW11bmljYXRpb25zLiAgSVB2NiBvZmZlcnMgb3Bw
b3J0dW5pdGllcyBmb3IgZGlyZWN0IGNvbW11bmljYXRpb24gDQo+ID4gdGhhdCBjYW4gbWFrZSB0
aGUgZXZlbnQgcXVldWUgYXBwcm9hY2ggb2Jzb2xldGUsIHNvIGl0J3Mgd29ydGggDQo+ID4gZXhh
bWluaW5nIElQdjYtb3JpZW50ZWQgYWx0ZXJuYXRpdmVzLg0KPiA+ICAgIOKAoiBXZSByZWNlbnRs
eSBkaXNjdXNzZWQgZmVhdHVyZSBhbmQgcHJvdG9jb2wgbmVnb3RpYXRpb24gd2l0aGluIA0KPiA+
IFZXUkFQLiAgSVB2NiBwcm92aWRlcyBtdWNoIG9wcG9ydHVuaXR5IGZvciBuZXcgZmVhdHVyZXMg
YW5kIHByb3RvY29sIA0KPiA+IHBhdGh3YXlzIHRvIGJlIG5lZ290aWF0ZWQgYmV0d2VlbiBlbmRw
b2ludHMsIHNvIGl0IGdpdmVzIHVzIGEgdmVyeSANCj4gPiByZWFsIGFuZCBpbW1pbmVudCBzZXQg
b2YgdXNlIGNhc2VzIGZvciBuZWdvdGlhdGlvbi4NCj4gPg0KPiA+IEl0IHdvdWxkIGFsc28gYmUg
YSBmZWF0aGVyIGluIFZXUkFQJ3MgY2FwIHRvIGJlIGNvbnNpZGVyZWQgYW4gIklQdjYtIA0KPiA+
IGNhcGFibGUgYXBwbGljYXRpb24gcHJvdG9jb2wiIGluIGEgc3Ryb25nZXIgc2Vuc2UgdGhhbiBq
dXN0IHRvIGJlIA0KPiA+IGNhcnJpZWQgYnkgSVB2NiBuZXR3b3Jrcy4gIElQdjYgZG9lcyBhZnRl
ciBhbGwgYnJpbmcgbmV3IGFiaWxpdGllcyANCj4gPiB0byB0aGUgdGFibGUsIHN1Y2ggYXMgdGhl
IGh1Z2UgYWRkcmVzc2luZywgYW5kIGl0IHdvdWxkIGJlIGEgbWlzdGFrZSANCj4gPiB0byBpZ25v
cmUgdGhlbS4NCj4gPg0KPiA+DQo+ID4gTW9yZ2FpbmUuDQo+ID4NCj4gPg0KPiA+DQo+ID4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiB2d3JhcCBt
YWlsaW5nIGxpc3QNCj4gPiB2d3JhcEBpZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vdndyYXANCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+IHZ3cmFwIG1haWxpbmcgbGlzdA0KPiB2d3JhcEBpZXRm
Lm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Z3cmFwDQoNCg==
--=_alternative 00518F0D85257726_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

DQo8YnI+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj52d3JhcC1ib3VuY2VzQGlldGYub3JnIHdyb3Rl
IG9uIDA1LzE3LzIwMTAgMTA6MDg6MjYNCkFNOjxicj4NCjxicj4NCiZndDsgW2ltYWdlIHJlbW92
ZWRdIDwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+DQomZ3Q7IFJl
OiBbdndyYXBdIFZXUkFQIGFuZCBJUHY2PC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9
Mj4mZ3Q7IDxicj4NCiZndDsgUmljaGFyZCBCYXJuZXMgPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxm
b250IHNpemU9Mj4mZ3Q7IDxicj4NCiZndDsgdG86PC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250
IHNpemU9Mj4mZ3Q7IDxicj4NCiZndDsgTW9yZ2FpbmU8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZv
bnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyAwNS8xNy8yMDEwIDEwOjA5IEFNPC9mb250PjwvdHQ+
DQo8YnI+PHR0Pjxmb250IHNpemU9Mj4mZ3Q7IDxicj4NCiZndDsgU2VudCBieTo8L2ZvbnQ+PC90
dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyB2d3JhcC1ib3VuY2VzQGll
dGYub3JnPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj4mZ3Q7IDxicj4NCiZndDsg
Q2M6PC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj4mZ3Q7IDxicj4NCiZndDsgdndy
YXA8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyBJbiB0
aGUgc3Bpcml0IG9mIGdvb2QgbGF5ZXJpbmcsIGl0IHNlZW1zIGxpa2Ugd2Ugc2hvdWxkIGJlIHRh
bGtpbmcNCiZuYnNwOzxicj4NCiZndDsgYWJvdXQgYXZvaWRpbmcgZGlyZWN0IHJlbGlhbmNlIG9u
IElQIGFkZHJlc3NlcyBpbnN0ZWFkIG9mIGhvdyB3ZSBjYW4NCiZuYnNwOzxicj4NCiZndDsgYWNj
b21tb2RhdGUgZGlmZmVyZW50IGFkZHJlc3NlcyBpbiB0aGUgcHJvdG9jb2wuICZuYnNwO1doeSBp
cyB0aGVyZQ0KZXZlciBhICZuYnNwOzxicj4NCiZndDsgbmVlZCB0byBjYXJyeSBhbiBJUCBhZGRy
ZXNzIGluIHRoaXMgYXBwbGljYXRpb24tbGF5ZXIgcHJvdG9jb2wsIGFzDQombmJzcDs8YnI+DQom
Z3Q7IG9wcG9zZWQgdG8sIHNheSwgYSBETlMgbmFtZSBvciBhIFVSST88YnI+DQomZ3Q7IDxicj4N
CiZndDsgLS1SaWNoYXJkPGJyPg0KJmd0OyA8YnI+DQorMSA8L2ZvbnQ+PC90dD4NCjxicj4NCjxi
cj48dHQ+PGZvbnQgc2l6ZT0yPldlIG1heSBmcm9tIHRpbWUgdG8gdGltZSBoYXZlIGEgSVAgYWRk
cmVzcyBzdHVjayBpbg0KdGhlIGZvcm0gb2YgYSBVUkk8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZv
bnQgc2l6ZT0yPndoaWNoIGhhcyB0aGUgZG90dGVkIGRlY2ltYWwgZm9ybSBvZiBhbiByZXNvdXJj
ZS4NClRoZSBzcGVjIHNob3VsZCBtYWtlPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9
Mj5zdXJlIHRoYXQgZm9ybSBjYW4gYmUgYW4gSVBWNiBhZGRyZXNzLCBidXQgdGhhdCBzaG91bGQN
CmJlIHZlcnkgc3RyYWlnaHQgPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj5mb3J3
YXJkLiA8L2ZvbnQ+PC90dD4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPlRoZXJlIG1heSBi
ZSBzb21lIElQVjYgZmVhdHVyZXMgd2hpY2ggZXZlbnR1YWxseSBpbXBhY3QNCnVzIGF0IHRoZSBw
cm90b2NvbDwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+ZGVzaWduIGxldmVsLCBi
dXQgdGhlIGVudGlyZSBWV1JBUCBzcGVjaWZpY2F0aW9uIGhhcw0KYmVlbiB3cml0dGVuIGluIHRl
cm1zIG9mPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj5VUklzIGFuZCBDYXBhYmls
aXRpZXMsIG5vdCBpbiB0ZXJtcyBvZiBsb3cgbGV2ZWwgSVANCmFkZHJlc3Nlcy4gSXQgd291bGQg
dGFrZSBhbjwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+aW5jcmVkaWJseSBwb3dl
cmZ1bCBhcmd1bWVudCB0byBzdWdnZXN0IHRoYXQgdGhpcw0Kc2hvdWxkIGNoYW5nZS4gTGlrZXdp
c2UsIHdoaWxlPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj5JUFY2IGNoYW5nZXMg
YWRkcmVzc2luZyBhdCB0aGUgYm90dG9tIG9mIHRoZSBzdGFjaywNCml0IGRvZXNuJ3QgYXBwcmVj
aWFibHkgY2hhbmdlPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj50aGUgY29zdCBv
ZiBob2xkaW5nIG9wZW4gc2Vzc2lvbnMsIG9mIG1hbmFnaW5nIHNvY2tldHMNCmFuZCBidWZmZXJz
IGluc2lkZSBvZjwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Y2xpZW50cyAoZXNw
ZWNpYWxseSBsaWdodHdlaWdodCBkZXZpY2VzKSBGdXJ0aGVyIHdoaWxlDQp3ZSBjYW4gYWxsIGRl
dm91dGx5IGhvcGU8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPnRoYXQgSVBWNiBm
aW5hbGx5IGRlcGxveXMgYnJvYWRseSwgbWFraW5nIGl0IGEgZGVwZW5kYW5jeQ0KaW4gdGhlIG5l
YXIgdGVybSBmZWVsczwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+cmF0aGVyIGxp
a2UgYSByb2FkYmxvY2sgdG8gcG9zc2libGUgYWRvcHRpb24uPC9mb250PjwvdHQ+DQo8YnI+DQo8
YnI+PHR0Pjxmb250IHNpemU9Mj4tIERhdmlkPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNp
emU9Mj5+IFpoYTwvZm9udD48L3R0Pg0KPGJyPg0KPGJyPg0KPGJyPjx0dD48Zm9udCBzaXplPTI+
PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IE9uIE1heSAxNCwgMjAxMCwgYXQgNzozMiBBTSwgTW9yZ2Fp
bmUgd3JvdGU6PGJyPg0KJmd0OyA8YnI+DQomZ3Q7ICZndDsgRGVzcGl0ZSBleGNlZWRpbmdseSBs
b3cgdGFrZXVwIG9mIElQdjYgc28gZmFyLCBpdCdzIGNvbWluZywgYW5kDQppbiAmbmJzcDs8YnI+
DQomZ3Q7ICZndDsgdGhlIGNvbnRleHQgb2YgSUVURiBXRyByYXRlcyBvZiBwcm9ncmVzcywgaXQg
aXMgcmVhbGx5IGltbWluZW50Lg0KJm5ic3A7T2YgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHNwZWNp
YWwgcmVsZXZhbmNlIHRvIHVzIGlzIHRoYXQgSVB2NCBhZGRyZXNzZXMgYXJlIHByb2plY3RlZA0K
dG8gcnVuICZuYnNwOzxicj4NCiZndDsgJmd0OyBvdXQgd2l0aGluIHJvdWdobHkgdGhlIHNhbWUg
dGltZSBmcmFtZSBhcyBWV1JBUCBtYXRlcmlhbGl6ZXMuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0
OyAmZ3Q7IFRoZXJlIGlzIGxpdHRsZSBwb2ludCBpbiBjcmVhdGluZyBhIG5ldyBWVyBwcm90b2Nv
bCB0b2RheSBwdXJlbHkNCmluICZuYnNwOzxicj4NCiZndDsgJmd0OyB0aGUgY29udGV4dCBvZiBJ
UHY0IHdpdGhvdXQgdGhpbmtpbmcgYWJvdXQgdG9tb3Jyb3cncyBJUHY2ICZuYnNwOzxicj4NCiZn
dDsgJmd0OyBlbnZpcm9ubWVudC4gJm5ic3A7QnkgdGhlIHRpbWUgdGhhdCBWV1JBUCBpcyBmdWxs
eSBkZWZpbmVkLCB3ZQ0Kc2hvdWxkICZuYnNwOzxicj4NCiZndDsgJmd0OyBleHBlY3QgYSBzdWJz
dGFudGlhbCBhbmQgcmFwaWRseSBpbmNyZWFzaW5nIHByb3BvcnRpb24gb2YgVldSQVANCiZuYnNw
Ozxicj4NCiZndDsgJmd0OyBpbXBsZW1lbnRhdGlvbnMgdG8gb2NjdXIgaW4gSVB2Ni1hY2Nlc3Np
YmxlIHdvcmxkcy4gJm5ic3A7VGhpcw0KaXMgYSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgc2l0dWF0
aW9uIGZvciB3aGljaCB3ZSBuZWVkIHRvIHBsYW4gbm93LCBvdGhlcndpc2UgdGhlIHByb3RvY29s
DQp3aWxsICZuYnNwOzxicj4NCiZndDsgJmd0OyBiZSBvYnNvbGV0ZSBiZWZvcmUgaXQncyBldmVu
IHJlYWR5Ljxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBUbyBnZXQgdGhlIGJhbGwgcm9s
bGluZywgaGVyZSBhcmUgYSBmZXcgSVB2Ni1yZWxhdGVkIGlzc3VlcyB0aGF0DQp3ZSAmbmJzcDs8
YnI+DQomZ3Q7ICZndDsgY291bGQgdXNlZnVsbHkgYWRkcmVzcyBpbiB0aGUgZ3JvdXA6PGJyPg0K
Jmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDvigKIgVGhlIDEyOC1iaXQgSVAg
YWRkcmVzcyBvZiBJUHY2IGlzIGxpa2VseSB0byBiZWNvbWUNCmEgY29tbW9uICZuYnNwOzxicj4N
CiZndDsgJmd0OyBwYXlsb2FkLCBzbyBpdCBzaG91bGQgYmUgc3VwcG9ydGVkIG5hdGl2ZWx5LiAm
bmJzcDtMTFNEIGFscmVhZHkNCnN1cHBvcnRzICZuYnNwOzxicj4NCiZndDsgJmd0OyBvbmUgMTI4
LWJpdCBkYXRhIHR5cGUgb2YgY291cnNlLCB0aGUgVVVJRC4gJm5ic3A7SVB2NiBhZGRyZXNzZXMN
CnNob3VsZCAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgbm90IGJlIHRyYW5zcG9ydGVkIGluIFVVSUQg
ZmllbGRzIGhvd2V2ZXIsIHNpbmNlIHRoZWlyIHN0YXRpc3RpY2FsDQombmJzcDs8YnI+DQomZ3Q7
ICZndDsgcHJvcGVydGllcyBhbmQgc2VtYW50aWNzIGFyZSB0b3RhbGx5IGRpZmZlcmVudC4gJm5i
c3A7SW4gYW55DQpjYXNlLCB0aGUgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHR3byBzcGFjZXMgYXJl
IGRpc2pvaW50IHNvIGNvbmZ1c2luZyB0aGVtIHdvdWxkIGJlIGEgbWlzdGFrZS4NCiZuYnNwO1Ro
ZSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgSVB2NiBhZGRyZXNzIHNlZW1zIGEgZ29vZCBjYW5kaWRh
dGUgZm9yIGl0cyBvd24gZGVmaW5lZCB0eXBlLA0KaW4gdGhlICZuYnNwOzxicj4NCiZndDsgJmd0
OyBhYnNlbmNlIG9mIHdpZGUgaW50ZWdlcnMuPGJyPg0KJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDvi
gKIgVGhlIGV4dHJlbWVseSBsYXJnZSBhZGRyZXNzIHNwYWNlIG9mIElQdjYgaGFzDQpvZnRlbiBi
ZWVuICZuYnNwOzxicj4NCiZndDsgJmd0OyBwb3J0cmF5ZWQgYXMgYWxsb3dpbmcgZXZlcnl0aGlu
ZyBhcm91bmQgdXMgdG8gaGF2ZSBpdHMgb3duIElQDQombmJzcDs8YnI+DQomZ3Q7ICZndDsgYWRk
cmVzcy4gJm5ic3A7SW4gdGhlIGNvbnRleHQgb2YgdmlydHVhbCB3b3JsZHMsIHRoaXMgaWRlYSBj
YW4NCmFjdHVhbGx5ICZuYnNwOzxicj4NCiZndDsgJmd0OyBiZSBwdXQgdG8gZ29vZCB1c2UsIHdp
dGggZWFjaCB2aXJ0dWFsIG9iamVjdCBiZWFyaW5nIGl0cyBvd24NCklQdjYgJm5ic3A7PGJyPg0K
Jmd0OyAmZ3Q7IGFkZHJlc3MuICZuYnNwO09uZSBjYW5kaWRhdGUgYXBwbGljYXRpb24gZm9yIHRo
aXMgaGFzIGFscmVhZHkNCmJlZW4gJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGRlc2NyaWJlZCBpbiBl
YXJsaWVyIGRpc2N1c3Npb25zIC0tLSBmb3IgZXhhbXBsZSwgaW1wbGVtZW50aW5nDQombmJzcDs8
YnI+DQomZ3Q7ICZndDsgdmlydHVhbCBvYmplY3Qgc2ltdWxhdGlvbiBpbiB0d28gcGFydHMsIG9u
ZSBjbGllbnQtc2lkZSBhbmQgb25lDQombmJzcDs8YnI+DQomZ3Q7ICZndDsgd29ybGQtc2lkZSwg
dGhlIHR3byBwYXJ0cyBjb21tdW5pY2F0aW5nIGRpcmVjdGx5LiAmbmJzcDtJUHY2DQphZGRyZXNz
aW5nICZuYnNwOzxicj4NCiZndDsgJmd0OyBvZiBvYmplY3RzIG1ha2VzIHRoaXMgcmVsYXRpdmVs
eSBlYXN5IHRvIGFjaGlldmUgZWZmaWNpZW50bHksDQpzbyBpdHMgJm5ic3A7PGJyPg0KJmd0OyAm
Z3Q7IGltcGxlbWVudGF0aW9uIGluIElQdjYtYmFzZWQgd29ybGRzIGlzIGFsbW9zdCBpbmV2aXRh
YmxlIGJlZm9yZQ0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGxvbmcuICZuYnNwO1ZXUkFQIHNob3Vs
ZCBiZSByZWFkeSBmb3IgdGhpcy48YnI+DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO+KAoiBUaGUg
ZXZlbnQgcXVldWUgaW4gY3VycmVudCBpbXBsZW1lbnRhdGlvbnMgcHJvdmlkZXMNCmFuIGluZGly
ZWN0ICZuYnNwOzxicj4NCiZndDsgJmd0OyBhbmQgaGlnaGx5IGluZWZmaWNpZW50IHdheSBvZiBh
Y2hpZXZpbmcgd29ybGQtdG8tY2xpZW50ICZuYnNwOzxicj4NCiZndDsgJmd0OyBjb21tdW5pY2F0
aW9ucy4gJm5ic3A7SVB2NiBvZmZlcnMgb3Bwb3J0dW5pdGllcyBmb3IgZGlyZWN0IGNvbW11bmlj
YXRpb24NCiZuYnNwOzxicj4NCiZndDsgJmd0OyB0aGF0IGNhbiBtYWtlIHRoZSBldmVudCBxdWV1
ZSBhcHByb2FjaCBvYnNvbGV0ZSwgc28gaXQncyB3b3J0aA0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7
IGV4YW1pbmluZyBJUHY2LW9yaWVudGVkIGFsdGVybmF0aXZlcy48YnI+DQomZ3Q7ICZndDsgJm5i
c3A7ICZuYnNwO+KAoiBXZSByZWNlbnRseSBkaXNjdXNzZWQgZmVhdHVyZSBhbmQgcHJvdG9jb2wg
bmVnb3RpYXRpb24NCndpdGhpbiAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgVldSQVAuICZuYnNwO0lQ
djYgcHJvdmlkZXMgbXVjaCBvcHBvcnR1bml0eSBmb3IgbmV3IGZlYXR1cmVzDQphbmQgcHJvdG9j
b2wgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHBhdGh3YXlzIHRvIGJlIG5lZ290aWF0ZWQgYmV0d2Vl
biBlbmRwb2ludHMsIHNvIGl0IGdpdmVzIHVzIGENCnZlcnkgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7
IHJlYWwgYW5kIGltbWluZW50IHNldCBvZiB1c2UgY2FzZXMgZm9yIG5lZ290aWF0aW9uLjxicj4N
CiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBJdCB3b3VsZCBhbHNvIGJlIGEgZmVhdGhlciBpbiBW
V1JBUCdzIGNhcCB0byBiZSBjb25zaWRlcmVkIGFuDQomcXVvdDtJUHY2LSA8YnI+DQomZ3Q7ICZn
dDsgY2FwYWJsZSBhcHBsaWNhdGlvbiBwcm90b2NvbCZxdW90OyBpbiBhIHN0cm9uZ2VyIHNlbnNl
IHRoYW4ganVzdA0KdG8gYmUgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGNhcnJpZWQgYnkgSVB2NiBu
ZXR3b3Jrcy4gJm5ic3A7SVB2NiBkb2VzIGFmdGVyIGFsbCBicmluZyBuZXcNCmFiaWxpdGllcyAm
bmJzcDs8YnI+DQomZ3Q7ICZndDsgdG8gdGhlIHRhYmxlLCBzdWNoIGFzIHRoZSBodWdlIGFkZHJl
c3NpbmcsIGFuZCBpdCB3b3VsZCBiZSBhDQptaXN0YWtlICZuYnNwOzxicj4NCiZndDsgJmd0OyB0
byBpZ25vcmUgdGhlbS48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZn
dDsgTW9yZ2FpbmUuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7
PGJyPg0KJmd0OyAmZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fPGJyPg0KJmd0OyAmZ3Q7IHZ3cmFwIG1haWxpbmcgbGlzdDxicj4NCiZndDsgJmd0OyB2
d3JhcEBpZXRmLm9yZzxicj4NCiZndDsgJmd0OyA8L2ZvbnQ+PC90dD48YSBocmVmPWh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXA+PHR0Pjxmb250IHNpemU9Mj5odHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Z3cmFwPC9mb250PjwvdHQ+PC9hPjx0
dD48Zm9udCBzaXplPTI+PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyB2d3JhcCBtYWlsaW5nIGxpc3Q8
YnI+DQomZ3Q7IHZ3cmFwQGlldGYub3JnPGJyPg0KJmd0OyA8L2ZvbnQ+PC90dD48YSBocmVmPWh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXA+PHR0Pjxmb250IHNpemU9
Mj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Z3cmFwPC9mb250PjwvdHQ+
PC9hPjx0dD48Zm9udCBzaXplPTI+PGJyPg0KPC9mb250PjwvdHQ+DQo=
--=_alternative 00518F0D85257726_=--

From ohmeadhbh@gmail.com  Tue May 18 11:02:24 2010
Return-Path: <ohmeadhbh@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB2E73A6A40 for <vwrap@core3.amsl.com>; Tue, 18 May 2010 11:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.965
X-Spam-Level: 
X-Spam-Status: No, score=-0.965 tagged_above=-999 required=5 tests=[AWL=-0.966, BAYES_50=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 1Jin5ixk+zsw for <vwrap@core3.amsl.com>; Tue, 18 May 2010 11:02:23 -0700 (PDT)
Received: from mail-qy0-f200.google.com (mail-qy0-f200.google.com [209.85.221.200]) by core3.amsl.com (Postfix) with ESMTP id 9C7BD3A69BC for <vwrap@ietf.org>; Tue, 18 May 2010 11:02:18 -0700 (PDT)
Received: by qyk38 with SMTP id 38so7139378qyk.17 for <vwrap@ietf.org>; Tue, 18 May 2010 11:02:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=ou0rsKr8pyYbcCvX1ZXWJ1g5+Zw6lIpXefKRdOnxlsM=; b=tZQSRlIg8Y3xDX/9uLgXNL7BvgfAaPB+nWKKJuNTaWb2fkRFE8cm4zTkn02J86i2FD IqMgbLvSD9adyiDrV3QRGOf5Ijg+Ebsh15M+V6e1rd4n4qWxb68yaaIXk3CvVqj49SCZ 13GGD4+62Jd8WXflryqjWWr4wD13aNCAU2/Zk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=uCPkZcfTc/HzgDAbebVWv4ZvUppjh4LMX4/se+Svoy9bdW3L2u0RnNnY93Q9qtL36T uAg+eNF3wJDUlHhX0SV1GAVIEw/yrbM20ku8KpMUUZcefLBJm+19Zr7w2YRwD8Ow5M6J /MeSjVcKSyqE6tEINmOyovOpiTrVqta0TyOK0=
Received: by 10.224.53.91 with SMTP id l27mr3976651qag.352.1274205726221; Tue,  18 May 2010 11:02:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.3.137 with HTTP; Tue, 18 May 2010 11:01:46 -0700 (PDT)
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Tue, 18 May 2010 11:01:46 -0700
Message-ID: <AANLkTikhbjLXcqChgbMSonoTXRc4lVgzBOnK_J0fs9_1@mail.gmail.com>
To: opensource-dev@lists.secondlife.com, vwrap@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [vwrap] "Future Proofing VWRAP" presentation from today's AWG meeting
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2010 18:02:24 -0000

hey peeps.

i had the pleasure of presenting a few slides on "Future Proofing
VWRAP" at today's AW Groupies meeting. If you missed it, here is the
link to the google presentation.

http://docs.google.com/present/view?id=df7ht8v8_9hqxdscfr

cheers!
meadhbh
--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com

From kari.lippert@gmail.com  Wed May 19 03:51:59 2010
Return-Path: <kari.lippert@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 051D23A6C65 for <vwrap@core3.amsl.com>; Wed, 19 May 2010 03:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 YFvm-hDVBR2S for <vwrap@core3.amsl.com>; Wed, 19 May 2010 03:51:57 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id E21233A696F for <vwrap@ietf.org>; Wed, 19 May 2010 03:48:48 -0700 (PDT)
Received: by wwb24 with SMTP id 24so517720wwb.31 for <vwrap@ietf.org>; Wed, 19 May 2010 03:48:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=mR42/p4zG2gGLPskn0+pzzPoUC0Lc7Sj5hdqSM7oTIc=; b=M5EMrL/vo69Fp+LMFQyGc8Yi6hWCebH2TYWCBWIxEPU5c+l9hMWyGmASXFkmCgozw1 qabhpfc/el77PGchDfYe3teFkQT6c7hlAAZWzy6G2gZbmEZN6cHiYT6ho32rXNAHfO+O woUO7+xzlQfBF22xpSydlky1cWPAOMaBWW7z0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Vr53vtib+NdDnYneYaHg+d9T58t4Tuk2OTjW7Cv/UOKyREfB6WItIrdKpL6JO553mP pExnkwvtCOelPGpffgWa1PprjuoDmxiVuVK+pOPtFS+d6sl6q4DcB6kgNK2tgVyKXJRO BmgHH1HLa4P6+/Jz9/pyJoOx8Kt3vLtpzvqEU=
MIME-Version: 1.0
Received: by 10.216.87.132 with SMTP id y4mr4974168wee.174.1274266118666; Wed,  19 May 2010 03:48:38 -0700 (PDT)
Received: by 10.216.10.207 with HTTP; Wed, 19 May 2010 03:48:38 -0700 (PDT)
In-Reply-To: <AANLkTikhbjLXcqChgbMSonoTXRc4lVgzBOnK_J0fs9_1@mail.gmail.com>
References: <AANLkTikhbjLXcqChgbMSonoTXRc4lVgzBOnK_J0fs9_1@mail.gmail.com>
Date: Wed, 19 May 2010 06:48:38 -0400
Message-ID: <AANLkTik59B84QXLiiql6aJ_Pahw73-OlYhlqulIqQxOI@mail.gmail.com>
From: Kari Lippert <kari.lippert@gmail.com>
To: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Content-Type: multipart/alternative; boundary=0016e6d99ba75a3a980486f033c1
Cc: vwrap@ietf.org, opensource-dev@lists.secondlife.com
Subject: Re: [vwrap] "Future Proofing VWRAP" presentation from today's AWG meeting
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2010 10:51:59 -0000

--0016e6d99ba75a3a980486f033c1
Content-Type: text/plain; charset=ISO-8859-1

Sorry I missed it - looks good :)


On Tue, May 18, 2010 at 2:01 PM, Meadhbh Hamrick <ohmeadhbh@gmail.com>wrote:

> hey peeps.
>
> i had the pleasure of presenting a few slides on "Future Proofing
> VWRAP" at today's AW Groupies meeting. If you missed it, here is the
> link to the google presentation.
>
> http://docs.google.com/present/view?id=df7ht8v8_9hqxdscfr
>
> cheers!
> meadhbh
> --
> meadhbh hamrick * it's pronounced "maeve"
> @OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>



-- 


http://kjlippert.wordpress.com/
http://community.webshots.com/user/MissGnomer

--0016e6d99ba75a3a980486f033c1
Content-Type: text/html; charset=ISO-8859-1

Sorry I missed it - looks good :)<div><br><br><div class="gmail_quote">On Tue, May 18, 2010 at 2:01 PM, Meadhbh Hamrick <span dir="ltr">&lt;<a href="mailto:ohmeadhbh@gmail.com">ohmeadhbh@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">hey peeps.<br>
<br>
i had the pleasure of presenting a few slides on &quot;Future Proofing<br>
VWRAP&quot; at today&#39;s AW Groupies meeting. If you missed it, here is the<br>
link to the google presentation.<br>
<br>
<a href="http://docs.google.com/present/view?id=df7ht8v8_9hqxdscfr" target="_blank">http://docs.google.com/present/view?id=df7ht8v8_9hqxdscfr</a><br>
<br>
cheers!<br>
meadhbh<br>
<font color="#888888">--<br>
meadhbh hamrick * it&#39;s pronounced &quot;maeve&quot;<br>
@OhMeadhbh * <a href="http://meadhbh.org/" target="_blank">http://meadhbh.org/</a> * <a href="mailto:OhMeadhbh@gmail.com">OhMeadhbh@gmail.com</a><br>
_______________________________________________<br>
vwrap mailing list<br>
<a href="mailto:vwrap@ietf.org">vwrap@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/vwrap" target="_blank">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br><br><br><a href="http://kjlippert.wordpress.com/">http://kjlippert.wordpress.com/</a><br><a href="http://community.webshots.com/user/MissGnomer">http://community.webshots.com/user/MissGnomer</a><br>

</div>

--0016e6d99ba75a3a980486f033c1--

From morgaine.dinova@googlemail.com  Wed May 19 06:40:58 2010
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CAC83A6CDC for <vwrap@core3.amsl.com>; Wed, 19 May 2010 06:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.892
X-Spam-Level: 
X-Spam-Status: No, score=0.892 tagged_above=-999 required=5 tests=[AWL=0.268,  BAYES_50=0.001, 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 hdGoeuuG5Jza for <vwrap@core3.amsl.com>; Wed, 19 May 2010 06:40:56 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 0230A28C0FC for <vwrap@ietf.org>; Wed, 19 May 2010 06:36:07 -0700 (PDT)
Received: by wyb32 with SMTP id 32so686564wyb.31 for <vwrap@ietf.org>; Wed, 19 May 2010 06:35:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=tkIZ9JzZegmzD3OpVpXA3La/xms/QUB2EF+sR962rR8=; b=VGD/OSxMl0sDz6zi578bw+zvD3lXDyyWDHExjn6yG8meN95YKuXH+hM3pTBGNVLYxv wp3jSu1Xw8TmiHp3AqpAR0gUfzOvzGZ/sIM8YUm60l1HeG1po7DyzTcxiBFHr8s/+4nT QNHZQD7tOM77DBLygK4vGrln+geFoc873rIKs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=v4mx8uhaVXm8CFYAGlubojDYN5VrOEkowRo7e+yKCuRr0t2Mi8WNEELvA5Zc79pHvW hlVWBdg38q5N5cOOYHMvBKSdj6qRPjhcFyVxqc9itjRLBaX53o4LowAyjwsm2ymFR0yH cpe2qxnCZC6qXja8snwDyuGMVdsEBh+eWcgqc=
MIME-Version: 1.0
Received: by 10.216.93.13 with SMTP id k13mr3235666wef.180.1274276157148; Wed,  19 May 2010 06:35:57 -0700 (PDT)
Received: by 10.216.26.132 with HTTP; Wed, 19 May 2010 06:35:57 -0700 (PDT)
In-Reply-To: <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com>
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com>
Date: Wed, 19 May 2010 14:35:57 +0100
Message-ID: <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d644efb14fb50486f289fc
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2010 13:40:58 -0000

--0016e6d644efb14fb50486f289fc
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

The impact of IPv6 on VWs is going to be far greater than you imagine, I
believe.  As things stand, VWRAP is being designed around the features and
limitations of IPv4 networking.  It will of course be able to ride on top o=
f
IPv6 as a transport, but unable to benefit from its improved feature set,
unless we provide the means to do so.

The question "Why is there ever a need to carry an IP address in this
application-layer protocol, as opposed to, say, a DNS name or a URI?"
suggests an IPv4 mindset, because in IPv6 it has a variety of possible
answers:  (i) When the DNS lookup has already been done and does not need t=
o
be done again, (ii) When a FQDN maps to multiple addresses, but you want to
refer to a specific one, (iii) When an IPv6 address does not have an
external address record, (iv) When the host is already known and the IP
address denotes something other than a physical NIC interface, or (v) When
listeners are allocated locally and dynamically for the current session
only, and their IP addresses need to be communicated to a peer --- this wil=
l
be an extremely common use case with IPv6.

In today's IPv4-based systems, it is normal for a user's machine to have a
single IP address, and for a client on that machine to talk to a server tha=
t
has a single customer-facing IP address too (although it may also have
others that are not public).  In IPv6-based systems, this simple scenario i=
s
still possible but represents only a special case among a new and vastly
expanded set of IPv6 use cases.

The smallest allocatable block of IPv6 address space is a /64, so 2^(128-64=
)
IP addresses is the number that most normal IPv6 users will have, although
the much larger /48 blocks of 2^80 addresses are commonly assigned to users
as well.  With such IP riches client-side, it is certain that they will be
used for something, and the obvious suggestion is to give every VW object a=
n
IPv6 address of its own.

Lest we forget, one of the most important properties of the REST paradigm i=
s
addressability, but the benefits of high addressability go far beyond the
Web.  This is a property that will become ubiquitous throughout networked
computing with IPv6.  It's probably no exaggeration to say that *everything=
*
will be getting its own IP address. :-)

Faced with that future, it's a mistake to think in IPv4 terms and consider
IPv6 addresses as merely denoting a host which can be obtained from its
FQDN.  That's IPv4 thinking, and represents only a very basic use case for
IPv6.  In more extended use cases, IPv6 addresses will become much more lik=
e
active local UUIDs than like today's host IP addresses.  They will be used
for inner-application addressing, for example to make every object in an
application an addressable micro-server.

VWRAP is being born into an IPv6 world, and it would be a mistake to
hardwire IPv4 thinking into its design.  We continually refer to the need
for extensibility and a desire to future-proof the protocol, but lip servic=
e
is not enough.  Adding IPv6 addresses to the underlying ADT would provide a
bare minimum level of thinking ahead to support VWRAP implementations that
embrace large numbers of communicating objects.  (A generally extensible AD=
T
would of course achieve the same thing, and more.)


Morgaine.







=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On Mon, May 17, 2010 at 3:50 PM, David W Levine <dwl@us.ibm.com> wrote:

>
>
> vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26 AM:
>
> > [image removed]
> >
> > Re: [vwrap] VWRAP and IPv6
> >
> > Richard Barnes
> >
> > to:
> >
> > Morgaine
> >
> > 05/17/2010 10:09 AM
> >
> > Sent by:
> >
> > vwrap-bounces@ietf.org
> >
> > Cc:
> >
> > vwrap
> >
> > In the spirit of good layering, it seems like we should be talking
> > about avoiding direct reliance on IP addresses instead of how we can
> > accommodate different addresses in the protocol.  Why is there ever a
> > need to carry an IP address in this application-layer protocol, as
> > opposed to, say, a DNS name or a URI?
> >
> > --Richard
> >
> +1
>
> We may from time to time have a IP address stuck in the form of a URI
> which has the dotted decimal form of an resource. The spec should make
> sure that form can be an IPV6 address, but that should be very straight
> forward.
>
> There may be some IPV6 features which eventually impact us at the protoco=
l
> design level, but the entire VWRAP specification has been written in term=
s
> of
> URIs and Capabilities, not in terms of low level IP addresses. It would
> take an
> incredibly powerful argument to suggest that this should change. Likewise=
,
> while
> IPV6 changes addressing at the bottom of the stack, it doesn't appreciabl=
y
> change
> the cost of holding open sessions, of managing sockets and buffers inside
> of
> clients (especially lightweight devices) Further while we can all devoutl=
y
> hope
> that IPV6 finally deploys broadly, making it a dependancy in the near ter=
m
> feels
> rather like a roadblock to possible adoption.
>
> - David
> ~ Zha
>
>
>
> >
> > On May 14, 2010, at 7:32 AM, Morgaine wrote:
> >
> > > Despite exceedingly low takeup of IPv6 so far, it's coming, and in
> > > the context of IETF WG rates of progress, it is really imminent.  Of
> > > special relevance to us is that IPv4 addresses are projected to run
> > > out within roughly the same time frame as VWRAP materializes.
> > >
> > > There is little point in creating a new VW protocol today purely in
> > > the context of IPv4 without thinking about tomorrow's IPv6
> > > environment.  By the time that VWRAP is fully defined, we should
> > > expect a substantial and rapidly increasing proportion of VWRAP
> > > implementations to occur in IPv6-accessible worlds.  This is a
> > > situation for which we need to plan now, otherwise the protocol will
> > > be obsolete before it's even ready.
> > >
> > > To get the ball rolling, here are a few IPv6-related issues that we
> > > could usefully address in the group:
> > >
> > >    =95 The 128-bit IP address of IPv6 is likely to become a common
> > > payload, so it should be supported natively.  LLSD already supports
> > > one 128-bit data type of course, the UUID.  IPv6 addresses should
> > > not be transported in UUID fields however, since their statistical
> > > properties and semantics are totally different.  In any case, the
> > > two spaces are disjoint so confusing them would be a mistake.  The
> > > IPv6 address seems a good candidate for its own defined type, in the
> > > absence of wide integers.
> > >    =95 The extremely large address space of IPv6 has often been
> > > portrayed as allowing everything around us to have its own IP
> > > address.  In the context of virtual worlds, this idea can actually
> > > be put to good use, with each virtual object bearing its own IPv6
> > > address.  One candidate application for this has already been
> > > described in earlier discussions --- for example, implementing
> > > virtual object simulation in two parts, one client-side and one
> > > world-side, the two parts communicating directly.  IPv6 addressing
> > > of objects makes this relatively easy to achieve efficiently, so its
> > > implementation in IPv6-based worlds is almost inevitable before
> > > long.  VWRAP should be ready for this.
> > >    =95 The event queue in current implementations provides an indirec=
t
> > > and highly inefficient way of achieving world-to-client
> > > communications.  IPv6 offers opportunities for direct communication
> > > that can make the event queue approach obsolete, so it's worth
> > > examining IPv6-oriented alternatives.
> > >    =95 We recently discussed feature and protocol negotiation within
> > > VWRAP.  IPv6 provides much opportunity for new features and protocol
> > > pathways to be negotiated between endpoints, so it gives us a very
> > > real and imminent set of use cases for negotiation.
> > >
> > > It would also be a feather in VWRAP's cap to be considered an "IPv6-
> > > capable application protocol" in a stronger sense than just to be
> > > carried by IPv6 networks.  IPv6 does after all bring new abilities
> > > to the table, such as the huge addressing, and it would be a mistake
> > > to ignore them.
> > >
> > >
> > > Morgaine.
> > >
> > >
> > >
> > > _______________________________________________
> > > vwrap mailing list
> > > vwrap@ietf.org
> > > https://www.ietf.org/mailman/listinfo/vwrap
> >
> > _______________________________________________
> > vwrap mailing list
> > vwrap@ietf.org
> > https://www.ietf.org/mailman/listinfo/vwrap
>

--0016e6d644efb14fb50486f289fc
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

The impact of IPv6 on VWs is going to be far greater than you imagine, I be=
lieve.=A0 As things stand, VWRAP is being designed around the features and =
limitations of IPv4 networking.=A0 It will of course be able to ride on top=
 of IPv6 as a transport, but unable to benefit from its improved feature se=
t, unless we provide the means to do so.<br>

<br>The question &quot;Why is there ever a need to carry an IP address in t=
his application-layer protocol, as opposed to, say, a DNS name or a URI?&qu=
ot; suggests an IPv4 mindset, because in IPv6 it has a variety of possible =
answers:=A0 (i) When the DNS lookup has already been done and does not need=
 to be done again, (ii) When a FQDN maps to multiple addresses, but you wan=
t to refer to a specific one, (iii) When an IPv6 address does not have an e=
xternal address record, (iv) When the host is already known and the IP addr=
ess denotes something other than a physical NIC interface, or (v) When list=
eners are allocated locally and dynamically for the current session only, a=
nd their IP addresses need to be communicated to a peer --- this will be an=
 extremely common use case with IPv6.<br>

<br>In today&#39;s IPv4-based systems, it is normal for a user&#39;s machin=
e to have a single IP address, and for a client on that machine to talk to =
a server that has a single customer-facing IP address too (although it may =
also have others that are not public).=A0 In IPv6-based systems, this simpl=
e scenario is still possible but represents only a special case among a new=
 and vastly expanded set of IPv6 use cases.<br>

<br>The smallest allocatable block of IPv6 address space is a /64, so 2^(12=
8-64) IP addresses is the number that most normal IPv6 users will have, alt=
hough the much larger /48 blocks of 2^80 addresses are commonly assigned to=
 users as well.=A0 With such IP riches client-side, it is certain that they=
 will be used for something, and the obvious suggestion is to give every VW=
 object an IPv6 address of its own.<br>

<br>Lest we forget, one of the most important properties of the REST paradi=
gm is addressability, but the benefits of high addressability go far beyond=
 the Web.=A0 This is a property that will become ubiquitous throughout netw=
orked computing with IPv6.=A0 It&#39;s probably no exaggeration to say that=
 *everything* will be getting its own IP address. :-)<br>

<br>Faced with that future, it&#39;s a mistake to think in IPv4 terms and c=
onsider IPv6 addresses as merely denoting a host which can be obtained from=
 its FQDN.=A0 That&#39;s IPv4 thinking, and represents only a very basic us=
e case for IPv6.=A0 In more extended use cases, IPv6 addresses will become =
much more like active local UUIDs than like today&#39;s host IP addresses.=
=A0 They will be used for inner-application addressing, for example to make=
 every object in an application an addressable micro-server.<br>

<br>VWRAP is being born into an IPv6 world, and it would be a mistake to ha=
rdwire IPv4 thinking into its design.=A0 We continually refer to the need f=
or extensibility and a desire to future-proof the protocol, but lip service=
 is not enough.=A0 Adding IPv6 addresses to the underlying ADT would provid=
e a bare minimum level of thinking ahead to support VWRAP implementations t=
hat embrace large numbers of communicating objects.=A0 (A generally extensi=
ble ADT would of course achieve the same thing, and more.)<br>
<br><br>Morgaine.<br><br><br><br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br><div class=3D"gmail_quote">O=
n Mon, May 17, 2010 at 3:50 PM, David W Levine <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:dwl@us.ibm.com" target=3D"_blank">dwl@us.ibm.com</a>&gt;</span>=
 wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br><tt><font size=3D"2"><a href=3D"mailto:vwrap-bounces@ietf.org" target=
=3D"_blank">vwrap-bounces@ietf.org</a> wrote on 05/17/2010 10:08:26
AM:<br>
<br>
&gt; [image removed] </font></tt>
<br><tt><font size=3D"2">&gt; <br>
&gt; Re: [vwrap] VWRAP and IPv6</font></tt>
<br><tt><font size=3D"2">&gt; <br>
&gt; Richard Barnes </font></tt>
<br><tt><font size=3D"2">&gt; <br>
&gt; to:</font></tt>
<br><tt><font size=3D"2">&gt; <br>
&gt; Morgaine</font></tt>
<br><tt><font size=3D"2">&gt; <br>
&gt; 05/17/2010 10:09 AM</font></tt>
<br><tt><font size=3D"2">&gt; <br>
&gt; Sent by:</font></tt>
<br><tt><font size=3D"2">&gt; <br>
&gt; <a href=3D"mailto:vwrap-bounces@ietf.org" target=3D"_blank">vwrap-boun=
ces@ietf.org</a></font></tt>
<br><tt><font size=3D"2">&gt; <br>
&gt; Cc:</font></tt>
<br><tt><font size=3D"2">&gt; <br>
&gt; vwrap</font></tt>
<br><tt><font size=3D"2"><div>&gt; <br>
&gt; In the spirit of good layering, it seems like we should be talking
=A0<br>
&gt; about avoiding direct reliance on IP addresses instead of how we can
=A0<br>
&gt; accommodate different addresses in the protocol. =A0Why is there
ever a =A0<br>
&gt; need to carry an IP address in this application-layer protocol, as
=A0<br>
&gt; opposed to, say, a DNS name or a URI?<br>
&gt; <br>
&gt; --Richard<br>
&gt; <br></div>
+1 </font></tt>
<br>
<br><tt><font size=3D"2">We may from time to time have a IP address stuck i=
n
the form of a URI</font></tt>
<br><tt><font size=3D"2">which has the dotted decimal form of an resource.
The spec should make</font></tt>
<br><tt><font size=3D"2">sure that form can be an IPV6 address, but that sh=
ould
be very straight </font></tt>
<br><tt><font size=3D"2">forward. </font></tt>
<br>
<br><tt><font size=3D"2">There may be some IPV6 features which eventually i=
mpact
us at the protocol</font></tt>
<br><tt><font size=3D"2">design level, but the entire VWRAP specification h=
as
been written in terms of</font></tt>
<br><tt><font size=3D"2">URIs and Capabilities, not in terms of low level I=
P
addresses. It would take an</font></tt>
<br><tt><font size=3D"2">incredibly powerful argument to suggest that this
should change. Likewise, while</font></tt>
<br><tt><font size=3D"2">IPV6 changes addressing at the bottom of the stack=
,
it doesn&#39;t appreciably change</font></tt>
<br><tt><font size=3D"2">the cost of holding open sessions, of managing soc=
kets
and buffers inside of</font></tt>
<br><tt><font size=3D"2">clients (especially lightweight devices) Further w=
hile
we can all devoutly hope</font></tt>
<br><tt><font size=3D"2">that IPV6 finally deploys broadly, making it a dep=
endancy
in the near term feels</font></tt>
<br><tt><font size=3D"2">rather like a roadblock to possible adoption.</fon=
t></tt>
<br>
<br><tt><font size=3D"2">- David</font></tt>
<br><tt><font size=3D"2">~ Zha</font></tt>
<br><div><div></div><div>
<br>
<br><tt><font size=3D"2"><br>
&gt; <br>
&gt; On May 14, 2010, at 7:32 AM, Morgaine wrote:<br>
&gt; <br>
&gt; &gt; Despite exceedingly low takeup of IPv6 so far, it&#39;s coming, a=
nd
in =A0<br>
&gt; &gt; the context of IETF WG rates of progress, it is really imminent.
=A0Of =A0<br>
&gt; &gt; special relevance to us is that IPv4 addresses are projected
to run =A0<br>
&gt; &gt; out within roughly the same time frame as VWRAP materializes.<br>
&gt; &gt;<br>
&gt; &gt; There is little point in creating a new VW protocol today purely
in =A0<br>
&gt; &gt; the context of IPv4 without thinking about tomorrow&#39;s IPv6 =
=A0<br>
&gt; &gt; environment. =A0By the time that VWRAP is fully defined, we
should =A0<br>
&gt; &gt; expect a substantial and rapidly increasing proportion of VWRAP
=A0<br>
&gt; &gt; implementations to occur in IPv6-accessible worlds. =A0This
is a =A0<br>
&gt; &gt; situation for which we need to plan now, otherwise the protocol
will =A0<br>
&gt; &gt; be obsolete before it&#39;s even ready.<br>
&gt; &gt;<br>
&gt; &gt; To get the ball rolling, here are a few IPv6-related issues that
we =A0<br>
&gt; &gt; could usefully address in the group:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0=95 The 128-bit IP address of IPv6 is likely to become
a common =A0<br>
&gt; &gt; payload, so it should be supported natively. =A0LLSD already
supports =A0<br>
&gt; &gt; one 128-bit data type of course, the UUID. =A0IPv6 addresses
should =A0<br>
&gt; &gt; not be transported in UUID fields however, since their statistica=
l
=A0<br>
&gt; &gt; properties and semantics are totally different. =A0In any
case, the =A0<br>
&gt; &gt; two spaces are disjoint so confusing them would be a mistake.
=A0The =A0<br>
&gt; &gt; IPv6 address seems a good candidate for its own defined type,
in the =A0<br>
&gt; &gt; absence of wide integers.<br>
&gt; &gt; =A0 =A0=95 The extremely large address space of IPv6 has
often been =A0<br>
&gt; &gt; portrayed as allowing everything around us to have its own IP
=A0<br>
&gt; &gt; address. =A0In the context of virtual worlds, this idea can
actually =A0<br>
&gt; &gt; be put to good use, with each virtual object bearing its own
IPv6 =A0<br>
&gt; &gt; address. =A0One candidate application for this has already
been =A0<br>
&gt; &gt; described in earlier discussions --- for example, implementing
=A0<br>
&gt; &gt; virtual object simulation in two parts, one client-side and one
=A0<br>
&gt; &gt; world-side, the two parts communicating directly. =A0IPv6
addressing =A0<br>
&gt; &gt; of objects makes this relatively easy to achieve efficiently,
so its =A0<br>
&gt; &gt; implementation in IPv6-based worlds is almost inevitable before
=A0<br>
&gt; &gt; long. =A0VWRAP should be ready for this.<br>
&gt; &gt; =A0 =A0=95 The event queue in current implementations provides
an indirect =A0<br>
&gt; &gt; and highly inefficient way of achieving world-to-client =A0<br>
&gt; &gt; communications. =A0IPv6 offers opportunities for direct communica=
tion
=A0<br>
&gt; &gt; that can make the event queue approach obsolete, so it&#39;s wort=
h
=A0<br>
&gt; &gt; examining IPv6-oriented alternatives.<br>
&gt; &gt; =A0 =A0=95 We recently discussed feature and protocol negotiation
within =A0<br>
&gt; &gt; VWRAP. =A0IPv6 provides much opportunity for new features
and protocol =A0<br>
&gt; &gt; pathways to be negotiated between endpoints, so it gives us a
very =A0<br>
&gt; &gt; real and imminent set of use cases for negotiation.<br>
&gt; &gt;<br>
&gt; &gt; It would also be a feather in VWRAP&#39;s cap to be considered an
&quot;IPv6- <br>
&gt; &gt; capable application protocol&quot; in a stronger sense than just
to be =A0<br>
&gt; &gt; carried by IPv6 networks. =A0IPv6 does after all bring new
abilities =A0<br>
&gt; &gt; to the table, such as the huge addressing, and it would be a
mistake =A0<br>
&gt; &gt; to ignore them.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Morgaine.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; vwrap mailing list<br>
&gt; &gt; <a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.or=
g</a><br>
&gt; &gt; </font></tt><a href=3D"https://www.ietf.org/mailman/listinfo/vwra=
p" target=3D"_blank"><tt><font size=3D"2">https://www.ietf.org/mailman/list=
info/vwrap</font></tt></a><tt><font size=3D"2"><br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; vwrap mailing list<br>
&gt; <a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a>=
<br>
&gt; </font></tt><a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" ta=
rget=3D"_blank"><tt><font size=3D"2">https://www.ietf.org/mailman/listinfo/=
vwrap</font></tt></a><tt><font size=3D"2"><br>
</font></tt>
</div></div></blockquote></div><br>

--0016e6d644efb14fb50486f289fc--

From rbarnes@bbn.com  Wed May 19 14:57:00 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DB4B28C0D8 for <vwrap@core3.amsl.com>; Wed, 19 May 2010 14:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.927
X-Spam-Level: 
X-Spam-Status: No, score=-0.927 tagged_above=-999 required=5 tests=[AWL=-0.928, BAYES_50=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 q8WZ3hIcNvza for <vwrap@core3.amsl.com>; Wed, 19 May 2010 14:56:59 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 5925D3A6AB7 for <vwrap@ietf.org>; Wed, 19 May 2010 14:56:49 -0700 (PDT)
Received: from ros-dhcp192-1-51-90.bbn.com ([192.1.51.90]:53135) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OErFp-000IOJ-OI for vwrap@ietf.org; Wed, 19 May 2010 17:56:41 -0400
Message-Id: <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com>
From: Richard Barnes <rbarnes@bbn.com>
To: vwrap@ietf.org
In-Reply-To: <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 19 May 2010 17:56:41 -0400
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2010 21:57:00 -0000

The impact of IPv6 on VWs should be far less than you imagine, I =20
think. :)

It has often been said that many, many things will be assigned IPv6 =20
addresses.  There will certainly be enough to go around, but that =20
doesn't make them good application-layer identifiers.  If you want to =20=

use IP addresses with IP, they have to route, and that means that they =20=

have to be either (1) topologically assigned, or (2) overlay routed, =20
e.g., with mobile IP.  So if you want to use an IP address to address =20=

something, you're going to have to either change that address when the =20=

thing gets connected differently, or you'll need some overlay routing =20=

scheme to route to a persistent address.  (And if you're not going to =20=

use the address with IP, then why would you use an IP address?)

VWRAP, as an application layer protocol, has a choice about what =20
identifiers to use for things and how to use those identifiers.  ISTM =20=

that using IP addresses (again, of either type) remains a bad idea, =20
compared with something that is decoupled from the routing layer.

As far as the DNS, I'm not sure what your point is:
(i) DNS caching has been around for decades
(ii) DNS names can already refer to multiple addresses
(iii) Depends on implementation.  Maybe there's some application-layer =20=

way to resolve names.  E.g., SIP endpoints don't need to have DNS =20
records because the INVITE transaction maps from SIP URIs to IP =20
addresses.
(iv) =46rom RFC 4291: "IPv6 addresses are 128-bit identifiers for =20
interfaces and sets of
interfaces"
(v) Seems like there's a use case lurking, hard to address without =20
details.  But you're probably still at the application layer.  For =20
instance, if you were telling your peer to send you an HTTP request, =20
you would send an HTTP URI, which can already handle IPv6 addresses.

--Richard


On May 19, 2010, at 9:35 AM, Morgaine wrote:

> The impact of IPv6 on VWs is going to be far greater than you =20
> imagine, I believe.  As things stand, VWRAP is being designed around =20=

> the features and limitations of IPv4 networking.  It will of course =20=

> be able to ride on top of IPv6 as a transport, but unable to benefit =20=

> from its improved feature set, unless we provide the means to do so.
>
> The question "Why is there ever a need to carry an IP address in =20
> this application-layer protocol, as opposed to, say, a DNS name or a =20=

> URI?" suggests an IPv4 mindset, because in IPv6 it has a variety of =20=

> possible answers:  (i) When the DNS lookup has already been done and =20=

> does not need to be done again, (ii) When a FQDN maps to multiple =20
> addresses, but you want to refer to a specific one, (iii) When an =20
> IPv6 address does not have an external address record, (iv) When the =20=

> host is already known and the IP address denotes something other =20
> than a physical NIC interface, or (v) When listeners are allocated =20
> locally and dynamically for the current session only, and their IP =20
> addresses need to be communicated to a peer --- this will be an =20
> extremely common use case with IPv6.
>
> In today's IPv4-based systems, it is normal for a user's machine to =20=

> have a single IP address, and for a client on that machine to talk =20
> to a server that has a single customer-facing IP address too =20
> (although it may also have others that are not public).  In IPv6-=20
> based systems, this simple scenario is still possible but represents =20=

> only a special case among a new and vastly expanded set of IPv6 use =20=

> cases.
>
> The smallest allocatable block of IPv6 address space is a /64, so =20
> 2^(128-64) IP addresses is the number that most normal IPv6 users =20
> will have, although the much larger /48 blocks of 2^80 addresses are =20=

> commonly assigned to users as well.  With such IP riches client-=20
> side, it is certain that they will be used for something, and the =20
> obvious suggestion is to give every VW object an IPv6 address of its =20=

> own.
>
> Lest we forget, one of the most important properties of the REST =20
> paradigm is addressability, but the benefits of high addressability =20=

> go far beyond the Web.  This is a property that will become =20
> ubiquitous throughout networked computing with IPv6.  It's probably =20=

> no exaggeration to say that *everything* will be getting its own IP =20=

> address. :-)
>
> Faced with that future, it's a mistake to think in IPv4 terms and =20
> consider IPv6 addresses as merely denoting a host which can be =20
> obtained from its FQDN.  That's IPv4 thinking, and represents only a =20=

> very basic use case for IPv6.  In more extended use cases, IPv6 =20
> addresses will become much more like active local UUIDs than like =20
> today's host IP addresses.  They will be used for inner-application =20=

> addressing, for example to make every object in an application an =20
> addressable micro-server.
>
> VWRAP is being born into an IPv6 world, and it would be a mistake to =20=

> hardwire IPv4 thinking into its design.  We continually refer to the =20=

> need for extensibility and a desire to future-proof the protocol, =20
> but lip service is not enough.  Adding IPv6 addresses to the =20
> underlying ADT would provide a bare minimum level of thinking ahead =20=

> to support VWRAP implementations that embrace large numbers of =20
> communicating objects.  (A generally extensible ADT would of course =20=

> achieve the same thing, and more.)
>
>
> Morgaine.
>
>
>
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> On Mon, May 17, 2010 at 3:50 PM, David W Levine <dwl@us.ibm.com> =20
> wrote:
>
>
> vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26 AM:
>
> > [image removed]
> >
> > Re: [vwrap] VWRAP and IPv6
> >
> > Richard Barnes
> >
> > to:
> >
> > Morgaine
> >
> > 05/17/2010 10:09 AM
> >
> > Sent by:
> >
> > vwrap-bounces@ietf.org
> >
> > Cc:
> >
> > vwrap
> >
> > In the spirit of good layering, it seems like we should be talking
> > about avoiding direct reliance on IP addresses instead of how we can
> > accommodate different addresses in the protocol.  Why is there =20
> ever a
> > need to carry an IP address in this application-layer protocol, as
> > opposed to, say, a DNS name or a URI?
> >
> > --Richard
> >
> +1
>
> We may from time to time have a IP address stuck in the form of a URI
> which has the dotted decimal form of an resource. The spec should make
> sure that form can be an IPV6 address, but that should be very =20
> straight
> forward.
>
> There may be some IPV6 features which eventually impact us at the =20
> protocol
> design level, but the entire VWRAP specification has been written in =20=

> terms of
> URIs and Capabilities, not in terms of low level IP addresses. It =20
> would take an
> incredibly powerful argument to suggest that this should change. =20
> Likewise, while
> IPV6 changes addressing at the bottom of the stack, it doesn't =20
> appreciably change
> the cost of holding open sessions, of managing sockets and buffers =20
> inside of
> clients (especially lightweight devices) Further while we can all =20
> devoutly hope
> that IPV6 finally deploys broadly, making it a dependancy in the =20
> near term feels
> rather like a roadblock to possible adoption.
>
> - David
> ~ Zha
>
>
>
> >
> > On May 14, 2010, at 7:32 AM, Morgaine wrote:
> >
> > > Despite exceedingly low takeup of IPv6 so far, it's coming, and in
> > > the context of IETF WG rates of progress, it is really =20
> imminent.  Of
> > > special relevance to us is that IPv4 addresses are projected to =20=

> run
> > > out within roughly the same time frame as VWRAP materializes.
> > >
> > > There is little point in creating a new VW protocol today purely =20=

> in
> > > the context of IPv4 without thinking about tomorrow's IPv6
> > > environment.  By the time that VWRAP is fully defined, we should
> > > expect a substantial and rapidly increasing proportion of VWRAP
> > > implementations to occur in IPv6-accessible worlds.  This is a
> > > situation for which we need to plan now, otherwise the protocol =20=

> will
> > > be obsolete before it's even ready.
> > >
> > > To get the ball rolling, here are a few IPv6-related issues that =20=

> we
> > > could usefully address in the group:
> > >
> > >    =95 The 128-bit IP address of IPv6 is likely to become a common
> > > payload, so it should be supported natively.  LLSD already =20
> supports
> > > one 128-bit data type of course, the UUID.  IPv6 addresses should
> > > not be transported in UUID fields however, since their statistical
> > > properties and semantics are totally different.  In any case, the
> > > two spaces are disjoint so confusing them would be a mistake.  The
> > > IPv6 address seems a good candidate for its own defined type, in =20=

> the
> > > absence of wide integers.
> > >    =95 The extremely large address space of IPv6 has often been
> > > portrayed as allowing everything around us to have its own IP
> > > address.  In the context of virtual worlds, this idea can actually
> > > be put to good use, with each virtual object bearing its own IPv6
> > > address.  One candidate application for this has already been
> > > described in earlier discussions --- for example, implementing
> > > virtual object simulation in two parts, one client-side and one
> > > world-side, the two parts communicating directly.  IPv6 addressing
> > > of objects makes this relatively easy to achieve efficiently, so =20=

> its
> > > implementation in IPv6-based worlds is almost inevitable before
> > > long.  VWRAP should be ready for this.
> > >    =95 The event queue in current implementations provides an =20
> indirect
> > > and highly inefficient way of achieving world-to-client
> > > communications.  IPv6 offers opportunities for direct =20
> communication
> > > that can make the event queue approach obsolete, so it's worth
> > > examining IPv6-oriented alternatives.
> > >    =95 We recently discussed feature and protocol negotiation =
within
> > > VWRAP.  IPv6 provides much opportunity for new features and =20
> protocol
> > > pathways to be negotiated between endpoints, so it gives us a very
> > > real and imminent set of use cases for negotiation.
> > >
> > > It would also be a feather in VWRAP's cap to be considered an =20
> "IPv6-
> > > capable application protocol" in a stronger sense than just to be
> > > carried by IPv6 networks.  IPv6 does after all bring new abilities
> > > to the table, such as the huge addressing, and it would be a =20
> mistake
> > > to ignore them.
> > >
> > >
> > > Morgaine.
> > >
> > >
> > >
> > > _______________________________________________
> > > vwrap mailing list
> > > vwrap@ietf.org
> > > https://www.ietf.org/mailman/listinfo/vwrap
> >
> > _______________________________________________
> > vwrap mailing list
> > vwrap@ietf.org
> > https://www.ietf.org/mailman/listinfo/vwrap
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap


From bobby@sharedrealm.com  Wed May 19 16:45:51 2010
Return-Path: <bobby@sharedrealm.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 04F9E3A69DF for <vwrap@core3.amsl.com>; Wed, 19 May 2010 16:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 CfnxJ4dS-1Rz for <vwrap@core3.amsl.com>; Wed, 19 May 2010 16:45:49 -0700 (PDT)
Received: from mail.neoawareness.com (ns2.sharedrealm.com [IPv6:2001:470:1f05:4f4::13]) by core3.amsl.com (Postfix) with ESMTP id 92E463A68CF for <vwrap@ietf.org>; Wed, 19 May 2010 16:45:49 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=[10.200.0.30]) by mail.neoawareness.com with esmtpa (Exim 4.69) (envelope-from <bobby@sharedrealm.com>) id 1OEsxI-0001o1-Up for vwrap@ietf.org; Wed, 19 May 2010 16:45:41 -0700
From: "Robert G. Jakabosky" <bobby@sharedrealm.com>
To: vwrap@ietf.org
Date: Wed, 19 May 2010 16:45:50 -0700
User-Agent: KMail/1.9.9
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com>
In-Reply-To: <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201005191645.50835.bobby@sharedrealm.com>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bobby@sharedrealm.com
X-SA-Exim-Scanned: No (on mail.neoawareness.com); SAEximRunCond expanded to false
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2010 23:45:51 -0000

On Wednesday 19, Morgaine wrote:
> Faced with that future, it's a mistake to think in IPv4 terms and consider
> IPv6 addresses as merely denoting a host which can be obtained from its
> FQDN.  That's IPv4 thinking, and represents only a very basic use case for
> IPv6.  In more extended use cases, IPv6 addresses will become much more
> like active local UUIDs than like today's host IP addresses.  They will be
> used for inner-application addressing, for example to make every object in
> an application an addressable micro-server.

It is an interesting idea (making all objects directly addressable), but you 
are not thinking about the costs of dynamically binding large number of IPv6 
addresses to the server's NIC.  Think about the case where you have 100 
servers with 10,000 - 100,000 objects each, those servers will need to send 
out a lot of ARP traffic.  Also each server would need to have a very large 
ARP cache, and the border routers would need to handle advertising the routes 
for all those IPv6 addresses.  This will not scale well.

The only way to get around the routing/ARP issue would be to assign a block to 
each server and allocate IP addresses from the servers block for object on 
that server.  But then you can't move the object between servers with out 
changing it's IP address, which it would have to send a notice to all who 
where communicating with it.

Also besides the network routing/ARP traffic overhead, there is also overhead 
in the OS layer.  Have you even tested what the resource overhead is in the 
OS with 10,000 - 100,000 IPv6 addresses bound to a NIC?  How many open socket 
connections do you think the server will need to handle? or would the objects 
communicate with connection-less unreliable UDP?

Maybe you should try out this idea with working code to show what the 
costs/overhead will be in management a large number of IPv6 addresses.
For testing you can get some free /48 or /64 blocks of IPv6 addresses from: 
http://tunnelbroker.net/

> VWRAP is being born into an IPv6 world, and it would be a mistake to
> hardwire IPv4 thinking into its design.  We continually refer to the need
> for extensibility and a desire to future-proof the protocol, but lip
> service is not enough.  Adding IPv6 addresses to the underlying ADT would
> provide a bare minimum level of thinking ahead to support VWRAP
> implementations that embrace large numbers of communicating objects.  (A
> generally extensible ADT would of course achieve the same thing, and more.)

Even when IPv4 runs out there will be a lot of people stuck on IPv4 networks 
old routers, old DSL modems, ISPs who are slow to add IPv6 support.

I don't see anyone on this list trying to hardwire IPv4 into the design of 
VWRAP.  As long as the VWRAP doesn't keep the SL UDP protocol as-is with it's 
fixed IPv4 address data type.

VWRAP should support both IPv4 & IPv6.  I see no good reason to lock VWRAP to 
IPv6 only.

-- 
Robert G. Jakabosky

From morgaine.dinova@googlemail.com  Thu May 20 02:51:08 2010
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FC9A3A6AF2 for <vwrap@core3.amsl.com>; Thu, 20 May 2010 02:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.853
X-Spam-Level: 
X-Spam-Status: No, score=0.853 tagged_above=-999 required=5 tests=[AWL=0.229,  BAYES_50=0.001, 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 Po3FsIPWFW8W for <vwrap@core3.amsl.com>; Thu, 20 May 2010 02:51:06 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id E60E83A6A0E for <vwrap@ietf.org>; Thu, 20 May 2010 02:51:03 -0700 (PDT)
Received: by wyb32 with SMTP id 32so1417256wyb.31 for <vwrap@ietf.org>; Thu, 20 May 2010 02:50:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=hpwhjbYQVFhQdl0P4h1ycUz9iPDeLyUnfWMrCrOaKSM=; b=GT094WwaPoF/E3CTg/mahMOzr2L+AS7HUQwkxZJZF1csVvJ74QicvHFiEmpzminKzu hk6PSvM9JRHL2Ts0sOoBRuUPUSA1yNPTcvaKl7mLqXWDfNom6B8oEDmBA6qEZiXmaXRF pcTQoWiVc7YxI2rFbQjsuh5lTz4VQEXvYrjI4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VAxspkcVkQkZGcG+adyMxwmAkBfuhT9nfFheEWk/q3TBX5Ofy9SX9yJekiuODDk7b/ LBU6AARwfIxSkoWE5o93RwdJTmf6bgtfShpDh3J38RK1bstiwuUHo+Y6ZAXBg+FDghxi fW5fmZiFBApQUasakPLf+G9FD6SI+CFHsWOCk=
MIME-Version: 1.0
Received: by 10.216.86.149 with SMTP id w21mr5967445wee.221.1274349053921;  Thu, 20 May 2010 02:50:53 -0700 (PDT)
Received: by 10.216.26.132 with HTTP; Thu, 20 May 2010 02:50:53 -0700 (PDT)
In-Reply-To: <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com>
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com> <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com>
Date: Thu, 20 May 2010 10:50:53 +0100
Message-ID: <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d7ee5aadcd3904870382b5
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 09:51:08 -0000

--0016e6d7ee5aadcd3904870382b5
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

A /64 is the smallest routable IPv6 subnet, hence there is no extra routing
overhead for the 2^(128-64) addresses in the basic block that every user
will have allocated.

Needless to say, there won't be anything like 2^64 objects in your
scenegraph, so if you use your IPv6 address space to address every
scenegraph object that you have instantiated client-side, you will still
have an extremely sparsely used /64 block.  You'll be keeping track of whic=
h
addresses you have assigned dynamically of course. (An address space of thi=
s
size is not linearly scannable in realistic time.)

In principle this is no different to using UUIDs --- your IPv6 micro-server=
s
will have unguessable IPv6 addresses within your /64 block, and it'll be up
to you to tell other participants in the protocol (for example server-side
objects) with which of your IPv6 micro-servers they are to communicate.
This is why an ADT that is supportive of IPv6 operation needs to be able to
carry such data efficiently --- the UUID is no longer the only 128-bit datu=
m
of interest.

Of course your entire /64 block is routed as one, since there are no smalle=
r
routable subnets in IPv6, and therefore your objections about routing
non-scalability do not apply.


Morgaine.




=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On Wed, May 19, 2010 at 10:56 PM, Richard Barnes <rbarnes@bbn.com> wrote:

> The impact of IPv6 on VWs should be far less than you imagine, I think. :=
)
>
> It has often been said that many, many things will be assigned IPv6
> addresses.  There will certainly be enough to go around, but that doesn't
> make them good application-layer identifiers.  If you want to use IP
> addresses with IP, they have to route, and that means that they have to b=
e
> either (1) topologically assigned, or (2) overlay routed, e.g., with mobi=
le
> IP.  So if you want to use an IP address to address something, you're goi=
ng
> to have to either change that address when the thing gets connected
> differently, or you'll need some overlay routing scheme to route to a
> persistent address.  (And if you're not going to use the address with IP,
> then why would you use an IP address?)
>
> VWRAP, as an application layer protocol, has a choice about what
> identifiers to use for things and how to use those identifiers.  ISTM tha=
t
> using IP addresses (again, of either type) remains a bad idea, compared w=
ith
> something that is decoupled from the routing layer.
>
> As far as the DNS, I'm not sure what your point is:
> (i) DNS caching has been around for decades
> (ii) DNS names can already refer to multiple addresses
> (iii) Depends on implementation.  Maybe there's some application-layer wa=
y
> to resolve names.  E.g., SIP endpoints don't need to have DNS records
> because the INVITE transaction maps from SIP URIs to IP addresses.
> (iv) From RFC 4291: "IPv6 addresses are 128-bit identifiers for interface=
s
> and sets of
> interfaces"
> (v) Seems like there's a use case lurking, hard to address without detail=
s.
>  But you're probably still at the application layer.  For instance, if yo=
u
> were telling your peer to send you an HTTP request, you would send an HTT=
P
> URI, which can already handle IPv6 addresses.
>
> --Richard
>
>
>
> On May 19, 2010, at 9:35 AM, Morgaine wrote:
>
>  The impact of IPv6 on VWs is going to be far greater than you imagine, I
>> believe.  As things stand, VWRAP is being designed around the features a=
nd
>> limitations of IPv4 networking.  It will of course be able to ride on to=
p of
>> IPv6 as a transport, but unable to benefit from its improved feature set=
,
>> unless we provide the means to do so.
>>
>> The question "Why is there ever a need to carry an IP address in this
>> application-layer protocol, as opposed to, say, a DNS name or a URI?"
>> suggests an IPv4 mindset, because in IPv6 it has a variety of possible
>> answers:  (i) When the DNS lookup has already been done and does not nee=
d to
>> be done again, (ii) When a FQDN maps to multiple addresses, but you want=
 to
>> refer to a specific one, (iii) When an IPv6 address does not have an
>> external address record, (iv) When the host is already known and the IP
>> address denotes something other than a physical NIC interface, or (v) Wh=
en
>> listeners are allocated locally and dynamically for the current session
>> only, and their IP addresses need to be communicated to a peer --- this =
will
>> be an extremely common use case with IPv6.
>>
>> In today's IPv4-based systems, it is normal for a user's machine to have=
 a
>> single IP address, and for a client on that machine to talk to a server =
that
>> has a single customer-facing IP address too (although it may also have
>> others that are not public).  In IPv6-based systems, this simple scenari=
o is
>> still possible but represents only a special case among a new and vastly
>> expanded set of IPv6 use cases.
>>
>> The smallest allocatable block of IPv6 address space is a /64, so
>> 2^(128-64) IP addresses is the number that most normal IPv6 users will h=
ave,
>> although the much larger /48 blocks of 2^80 addresses are commonly assig=
ned
>> to users as well.  With such IP riches client-side, it is certain that t=
hey
>> will be used for something, and the obvious suggestion is to give every =
VW
>> object an IPv6 address of its own.
>>
>> Lest we forget, one of the most important properties of the REST paradig=
m
>> is addressability, but the benefits of high addressability go far beyond=
 the
>> Web.  This is a property that will become ubiquitous throughout networke=
d
>> computing with IPv6.  It's probably no exaggeration to say that *everyth=
ing*
>> will be getting its own IP address. :-)
>>
>> Faced with that future, it's a mistake to think in IPv4 terms and consid=
er
>> IPv6 addresses as merely denoting a host which can be obtained from its
>> FQDN.  That's IPv4 thinking, and represents only a very basic use case f=
or
>> IPv6.  In more extended use cases, IPv6 addresses will become much more =
like
>> active local UUIDs than like today's host IP addresses.  They will be us=
ed
>> for inner-application addressing, for example to make every object in an
>> application an addressable micro-server.
>>
>> VWRAP is being born into an IPv6 world, and it would be a mistake to
>> hardwire IPv4 thinking into its design.  We continually refer to the nee=
d
>> for extensibility and a desire to future-proof the protocol, but lip ser=
vice
>> is not enough.  Adding IPv6 addresses to the underlying ADT would provid=
e a
>> bare minimum level of thinking ahead to support VWRAP implementations th=
at
>> embrace large numbers of communicating objects.  (A generally extensible=
 ADT
>> would of course achieve the same thing, and more.)
>>
>>
>> Morgaine.
>>
>>
>>
>>
>>
>>
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> On Mon, May 17, 2010 at 3:50 PM, David W Levine <dwl@us.ibm.com> wrote:
>>
>>
>> vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26 AM:
>>
>> > [image removed]
>> >
>> > Re: [vwrap] VWRAP and IPv6
>> >
>> > Richard Barnes
>> >
>> > to:
>> >
>> > Morgaine
>> >
>> > 05/17/2010 10:09 AM
>> >
>> > Sent by:
>> >
>> > vwrap-bounces@ietf.org
>> >
>> > Cc:
>> >
>> > vwrap
>> >
>> > In the spirit of good layering, it seems like we should be talking
>> > about avoiding direct reliance on IP addresses instead of how we can
>> > accommodate different addresses in the protocol.  Why is there ever a
>> > need to carry an IP address in this application-layer protocol, as
>> > opposed to, say, a DNS name or a URI?
>> >
>> > --Richard
>> >
>> +1
>>
>> We may from time to time have a IP address stuck in the form of a URI
>> which has the dotted decimal form of an resource. The spec should make
>> sure that form can be an IPV6 address, but that should be very straight
>> forward.
>>
>> There may be some IPV6 features which eventually impact us at the protoc=
ol
>> design level, but the entire VWRAP specification has been written in ter=
ms
>> of
>> URIs and Capabilities, not in terms of low level IP addresses. It would
>> take an
>> incredibly powerful argument to suggest that this should change. Likewis=
e,
>> while
>> IPV6 changes addressing at the bottom of the stack, it doesn't appreciab=
ly
>> change
>> the cost of holding open sessions, of managing sockets and buffers insid=
e
>> of
>> clients (especially lightweight devices) Further while we can all devout=
ly
>> hope
>> that IPV6 finally deploys broadly, making it a dependancy in the near te=
rm
>> feels
>> rather like a roadblock to possible adoption.
>>
>> - David
>> ~ Zha
>>
>>
>>
>> >
>> > On May 14, 2010, at 7:32 AM, Morgaine wrote:
>> >
>> > > Despite exceedingly low takeup of IPv6 so far, it's coming, and in
>> > > the context of IETF WG rates of progress, it is really imminent.  Of
>> > > special relevance to us is that IPv4 addresses are projected to run
>> > > out within roughly the same time frame as VWRAP materializes.
>> > >
>> > > There is little point in creating a new VW protocol today purely in
>> > > the context of IPv4 without thinking about tomorrow's IPv6
>> > > environment.  By the time that VWRAP is fully defined, we should
>> > > expect a substantial and rapidly increasing proportion of VWRAP
>> > > implementations to occur in IPv6-accessible worlds.  This is a
>> > > situation for which we need to plan now, otherwise the protocol will
>> > > be obsolete before it's even ready.
>> > >
>> > > To get the ball rolling, here are a few IPv6-related issues that we
>> > > could usefully address in the group:
>> > >
>> > >    =95 The 128-bit IP address of IPv6 is likely to become a common
>> > > payload, so it should be supported natively.  LLSD already supports
>> > > one 128-bit data type of course, the UUID.  IPv6 addresses should
>> > > not be transported in UUID fields however, since their statistical
>> > > properties and semantics are totally different.  In any case, the
>> > > two spaces are disjoint so confusing them would be a mistake.  The
>> > > IPv6 address seems a good candidate for its own defined type, in the
>> > > absence of wide integers.
>> > >    =95 The extremely large address space of IPv6 has often been
>> > > portrayed as allowing everything around us to have its own IP
>> > > address.  In the context of virtual worlds, this idea can actually
>> > > be put to good use, with each virtual object bearing its own IPv6
>> > > address.  One candidate application for this has already been
>> > > described in earlier discussions --- for example, implementing
>> > > virtual object simulation in two parts, one client-side and one
>> > > world-side, the two parts communicating directly.  IPv6 addressing
>> > > of objects makes this relatively easy to achieve efficiently, so its
>> > > implementation in IPv6-based worlds is almost inevitable before
>> > > long.  VWRAP should be ready for this.
>> > >    =95 The event queue in current implementations provides an indire=
ct
>> > > and highly inefficient way of achieving world-to-client
>> > > communications.  IPv6 offers opportunities for direct communication
>> > > that can make the event queue approach obsolete, so it's worth
>> > > examining IPv6-oriented alternatives.
>> > >    =95 We recently discussed feature and protocol negotiation within
>> > > VWRAP.  IPv6 provides much opportunity for new features and protocol
>> > > pathways to be negotiated between endpoints, so it gives us a very
>> > > real and imminent set of use cases for negotiation.
>> > >
>> > > It would also be a feather in VWRAP's cap to be considered an "IPv6-
>> > > capable application protocol" in a stronger sense than just to be
>> > > carried by IPv6 networks.  IPv6 does after all bring new abilities
>> > > to the table, such as the huge addressing, and it would be a mistake
>> > > to ignore them.
>> > >
>> > >
>> > > Morgaine.
>> > >
>> > >
>> > >
>> > > _______________________________________________
>> > > vwrap mailing list
>> > > vwrap@ietf.org
>> > > https://www.ietf.org/mailman/listinfo/vwrap
>> >
>> > _______________________________________________
>> > vwrap mailing list
>> > vwrap@ietf.org
>> > https://www.ietf.org/mailman/listinfo/vwrap
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>

--0016e6d7ee5aadcd3904870382b5
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

A /64 is the smallest routable IPv6 subnet, hence there is no extra routing=
 overhead for the 2^(128-64) addresses in the basic block that every user w=
ill have allocated.<br><br>Needless to say, there won&#39;t be anything lik=
e 2^64 objects in your scenegraph, so if you use your IPv6 address space to=
 address every scenegraph object that you have instantiated client-side, yo=
u will still have an extremely sparsely used /64 block.=A0 You&#39;ll be ke=
eping track of which addresses you have assigned dynamically of course. (An=
 address space of this size is not linearly scannable in realistic time.)<b=
r>
<br>In principle this is no different to using UUIDs --- your IPv6 micro-se=
rvers will have unguessable IPv6 addresses within your /64 block, and it&#3=
9;ll be up to you to tell other participants in the protocol (for example s=
erver-side objects) with which of your IPv6 micro-servers they are to commu=
nicate.=A0 This is why an ADT that is supportive of IPv6 operation needs to=
 be able to carry such data efficiently --- the UUID is no longer the only =
128-bit datum of interest.<br>
<br>Of course your entire /64 block is routed as one, since there are no sm=
aller routable subnets in IPv6, and therefore your objections about routing=
 non-scalability do not apply.<br><br><br>Morgaine.<br><br><br><br><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br><div class=3D"gmail_quote">On W=
ed, May 19, 2010 at 10:56 PM, Richard Barnes <span dir=3D"ltr">&lt;<a href=
=3D"mailto:rbarnes@bbn.com">rbarnes@bbn.com</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 2=
04); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The impact of IPv6 on VWs should be far less than you imagine, I think. :)<=
br>
<br>
It has often been said that many, many things will be assigned IPv6 address=
es. =A0There will certainly be enough to go around, but that doesn&#39;t ma=
ke them good application-layer identifiers. =A0If you want to use IP addres=
ses with IP, they have to route, and that means that they have to be either=
 (1) topologically assigned, or (2) overlay routed, e.g., with mobile IP. =
=A0So if you want to use an IP address to address something, you&#39;re goi=
ng to have to either change that address when the thing gets connected diff=
erently, or you&#39;ll need some overlay routing scheme to route to a persi=
stent address. =A0(And if you&#39;re not going to use the address with IP, =
then why would you use an IP address?)<br>

<br>
VWRAP, as an application layer protocol, has a choice about what identifier=
s to use for things and how to use those identifiers. =A0ISTM that using IP=
 addresses (again, of either type) remains a bad idea, compared with someth=
ing that is decoupled from the routing layer.<br>

<br>
As far as the DNS, I&#39;m not sure what your point is:<br>
(i) DNS caching has been around for decades<br>
(ii) DNS names can already refer to multiple addresses<br>
(iii) Depends on implementation. =A0Maybe there&#39;s some application-laye=
r way to resolve names. =A0E.g., SIP endpoints don&#39;t need to have DNS r=
ecords because the INVITE transaction maps from SIP URIs to IP addresses.<b=
r>

(iv) From RFC 4291: &quot;IPv6 addresses are 128-bit identifiers for interf=
aces and sets of<br>
interfaces&quot;<br>
(v) Seems like there&#39;s a use case lurking, hard to address without deta=
ils. =A0But you&#39;re probably still at the application layer. =A0For inst=
ance, if you were telling your peer to send you an HTTP request, you would =
send an HTTP URI, which can already handle IPv6 addresses.<br>
<font color=3D"#888888">
<br>
--Richard</font><div><div></div><div class=3D"h5"><br>
<br>
<br>
On May 19, 2010, at 9:35 AM, Morgaine wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The impact of IPv6 on VWs is going to be far greater than you imagine, I be=
lieve. =A0As things stand, VWRAP is being designed around the features and =
limitations of IPv4 networking. =A0It will of course be able to ride on top=
 of IPv6 as a transport, but unable to benefit from its improved feature se=
t, unless we provide the means to do so.<br>

<br>
The question &quot;Why is there ever a need to carry an IP address in this =
application-layer protocol, as opposed to, say, a DNS name or a URI?&quot; =
suggests an IPv4 mindset, because in IPv6 it has a variety of possible answ=
ers: =A0(i) When the DNS lookup has already been done and does not need to =
be done again, (ii) When a FQDN maps to multiple addresses, but you want to=
 refer to a specific one, (iii) When an IPv6 address does not have an exter=
nal address record, (iv) When the host is already known and the IP address =
denotes something other than a physical NIC interface, or (v) When listener=
s are allocated locally and dynamically for the current session only, and t=
heir IP addresses need to be communicated to a peer --- this will be an ext=
remely common use case with IPv6.<br>

<br>
In today&#39;s IPv4-based systems, it is normal for a user&#39;s machine to=
 have a single IP address, and for a client on that machine to talk to a se=
rver that has a single customer-facing IP address too (although it may also=
 have others that are not public). =A0In IPv6-based systems, this simple sc=
enario is still possible but represents only a special case among a new and=
 vastly expanded set of IPv6 use cases.<br>

<br>
The smallest allocatable block of IPv6 address space is a /64, so 2^(128-64=
) IP addresses is the number that most normal IPv6 users will have, althoug=
h the much larger /48 blocks of 2^80 addresses are commonly assigned to use=
rs as well. =A0With such IP riches client-side, it is certain that they wil=
l be used for something, and the obvious suggestion is to give every VW obj=
ect an IPv6 address of its own.<br>

<br>
Lest we forget, one of the most important properties of the REST paradigm i=
s addressability, but the benefits of high addressability go far beyond the=
 Web. =A0This is a property that will become ubiquitous throughout networke=
d computing with IPv6. =A0It&#39;s probably no exaggeration to say that *ev=
erything* will be getting its own IP address. :-)<br>

<br>
Faced with that future, it&#39;s a mistake to think in IPv4 terms and consi=
der IPv6 addresses as merely denoting a host which can be obtained from its=
 FQDN. =A0That&#39;s IPv4 thinking, and represents only a very basic use ca=
se for IPv6. =A0In more extended use cases, IPv6 addresses will become much=
 more like active local UUIDs than like today&#39;s host IP addresses. =A0T=
hey will be used for inner-application addressing, for example to make ever=
y object in an application an addressable micro-server.<br>

<br>
VWRAP is being born into an IPv6 world, and it would be a mistake to hardwi=
re IPv4 thinking into its design. =A0We continually refer to the need for e=
xtensibility and a desire to future-proof the protocol, but lip service is =
not enough. =A0Adding IPv6 addresses to the underlying ADT would provide a =
bare minimum level of thinking ahead to support VWRAP implementations that =
embrace large numbers of communicating objects. =A0(A generally extensible =
ADT would of course achieve the same thing, and more.)<br>

<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
On Mon, May 17, 2010 at 3:50 PM, David W Levine &lt;<a href=3D"mailto:dwl@u=
s.ibm.com" target=3D"_blank">dwl@us.ibm.com</a>&gt; wrote:<br>
<br>
<br>
<a href=3D"mailto:vwrap-bounces@ietf.org" target=3D"_blank">vwrap-bounces@i=
etf.org</a> wrote on 05/17/2010 10:08:26 AM:<br>
<br>
&gt; [image removed]<br>
&gt;<br>
&gt; Re: [vwrap] VWRAP and IPv6<br>
&gt;<br>
&gt; Richard Barnes<br>
&gt;<br>
&gt; to:<br>
&gt;<br>
&gt; Morgaine<br>
&gt;<br>
&gt; 05/17/2010 10:09 AM<br>
&gt;<br>
&gt; Sent by:<br>
&gt;<br>
&gt; <a href=3D"mailto:vwrap-bounces@ietf.org" target=3D"_blank">vwrap-boun=
ces@ietf.org</a><br>
&gt;<br>
&gt; Cc:<br>
&gt;<br>
&gt; vwrap<br>
&gt;<br>
&gt; In the spirit of good layering, it seems like we should be talking<br>
&gt; about avoiding direct reliance on IP addresses instead of how we can<b=
r>
&gt; accommodate different addresses in the protocol. =A0Why is there ever =
a<br>
&gt; need to carry an IP address in this application-layer protocol, as<br>
&gt; opposed to, say, a DNS name or a URI?<br>
&gt;<br>
&gt; --Richard<br>
&gt;<br>
+1<br>
<br>
We may from time to time have a IP address stuck in the form of a URI<br>
which has the dotted decimal form of an resource. The spec should make<br>
sure that form can be an IPV6 address, but that should be very straight<br>
forward.<br>
<br>
There may be some IPV6 features which eventually impact us at the protocol<=
br>
design level, but the entire VWRAP specification has been written in terms =
of<br>
URIs and Capabilities, not in terms of low level IP addresses. It would tak=
e an<br>
incredibly powerful argument to suggest that this should change. Likewise, =
while<br>
IPV6 changes addressing at the bottom of the stack, it doesn&#39;t apprecia=
bly change<br>
the cost of holding open sessions, of managing sockets and buffers inside o=
f<br>
clients (especially lightweight devices) Further while we can all devoutly =
hope<br>
that IPV6 finally deploys broadly, making it a dependancy in the near term =
feels<br>
rather like a roadblock to possible adoption.<br>
<br>
- David<br>
~ Zha<br>
<br>
<br>
<br>
&gt;<br>
&gt; On May 14, 2010, at 7:32 AM, Morgaine wrote:<br>
&gt;<br>
&gt; &gt; Despite exceedingly low takeup of IPv6 so far, it&#39;s coming, a=
nd in<br>
&gt; &gt; the context of IETF WG rates of progress, it is really imminent. =
=A0Of<br>
&gt; &gt; special relevance to us is that IPv4 addresses are projected to r=
un<br>
&gt; &gt; out within roughly the same time frame as VWRAP materializes.<br>
&gt; &gt;<br>
&gt; &gt; There is little point in creating a new VW protocol today purely =
in<br>
&gt; &gt; the context of IPv4 without thinking about tomorrow&#39;s IPv6<br=
>
&gt; &gt; environment. =A0By the time that VWRAP is fully defined, we shoul=
d<br>
&gt; &gt; expect a substantial and rapidly increasing proportion of VWRAP<b=
r>
&gt; &gt; implementations to occur in IPv6-accessible worlds. =A0This is a<=
br>
&gt; &gt; situation for which we need to plan now, otherwise the protocol w=
ill<br>
&gt; &gt; be obsolete before it&#39;s even ready.<br>
&gt; &gt;<br>
&gt; &gt; To get the ball rolling, here are a few IPv6-related issues that =
we<br>
&gt; &gt; could usefully address in the group:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0=95 The 128-bit IP address of IPv6 is likely to become a c=
ommon<br>
&gt; &gt; payload, so it should be supported natively. =A0LLSD already supp=
orts<br>
&gt; &gt; one 128-bit data type of course, the UUID. =A0IPv6 addresses shou=
ld<br>
&gt; &gt; not be transported in UUID fields however, since their statistica=
l<br>
&gt; &gt; properties and semantics are totally different. =A0In any case, t=
he<br>
&gt; &gt; two spaces are disjoint so confusing them would be a mistake. =A0=
The<br>
&gt; &gt; IPv6 address seems a good candidate for its own defined type, in =
the<br>
&gt; &gt; absence of wide integers.<br>
&gt; &gt; =A0 =A0=95 The extremely large address space of IPv6 has often be=
en<br>
&gt; &gt; portrayed as allowing everything around us to have its own IP<br>
&gt; &gt; address. =A0In the context of virtual worlds, this idea can actua=
lly<br>
&gt; &gt; be put to good use, with each virtual object bearing its own IPv6=
<br>
&gt; &gt; address. =A0One candidate application for this has already been<b=
r>
&gt; &gt; described in earlier discussions --- for example, implementing<br=
>
&gt; &gt; virtual object simulation in two parts, one client-side and one<b=
r>
&gt; &gt; world-side, the two parts communicating directly. =A0IPv6 address=
ing<br>
&gt; &gt; of objects makes this relatively easy to achieve efficiently, so =
its<br>
&gt; &gt; implementation in IPv6-based worlds is almost inevitable before<b=
r>
&gt; &gt; long. =A0VWRAP should be ready for this.<br>
&gt; &gt; =A0 =A0=95 The event queue in current implementations provides an=
 indirect<br>
&gt; &gt; and highly inefficient way of achieving world-to-client<br>
&gt; &gt; communications. =A0IPv6 offers opportunities for direct communica=
tion<br>
&gt; &gt; that can make the event queue approach obsolete, so it&#39;s wort=
h<br>
&gt; &gt; examining IPv6-oriented alternatives.<br>
&gt; &gt; =A0 =A0=95 We recently discussed feature and protocol negotiation=
 within<br>
&gt; &gt; VWRAP. =A0IPv6 provides much opportunity for new features and pro=
tocol<br>
&gt; &gt; pathways to be negotiated between endpoints, so it gives us a ver=
y<br>
&gt; &gt; real and imminent set of use cases for negotiation.<br>
&gt; &gt;<br>
&gt; &gt; It would also be a feather in VWRAP&#39;s cap to be considered an=
 &quot;IPv6-<br>
&gt; &gt; capable application protocol&quot; in a stronger sense than just =
to be<br>
&gt; &gt; carried by IPv6 networks. =A0IPv6 does after all bring new abilit=
ies<br>
&gt; &gt; to the table, such as the huge addressing, and it would be a mist=
ake<br>
&gt; &gt; to ignore them.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Morgaine.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; vwrap mailing list<br>
&gt; &gt; <a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.or=
g</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D=
"_blank">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; vwrap mailing list<br>
&gt; <a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
</blockquote>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
</div></div></blockquote></div><br>

--0016e6d7ee5aadcd3904870382b5--

From han.sontse.sl@gmail.com  Thu May 20 03:00:18 2010
Return-Path: <han.sontse.sl@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B7EF3A6835 for <vwrap@core3.amsl.com>; Thu, 20 May 2010 03:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 0Qt5Xd8-i7t0 for <vwrap@core3.amsl.com>; Thu, 20 May 2010 03:00:15 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 8591D3A6812 for <vwrap@ietf.org>; Thu, 20 May 2010 03:00:15 -0700 (PDT)
Received: by pxi19 with SMTP id 19so4513377pxi.31 for <vwrap@ietf.org>; Thu, 20 May 2010 03:00:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:in-reply-to :mime-version:content-type:message-id:cc:from:subject:date:to :x-mailer; bh=jHhNjuf50iCCF6V2npY8HON0AQO6EqenxjDbsniYGn4=; b=iA9XKEcthcFPpvm3AYuKQ6mC1pw/nhRHhdAj+amgophxgzhu0dufwpuUZa9BTx10Wi bIRnDqOHRg8uqRqne8WI4+45EAiBq9kuMnJzhr2fJoJqpy5OUPkY3VGa/qjrZ+8KosSR IUgKJhJ1l6fbiAc2WrxIOU5lY2hI+lKO8mdL8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-type:message-id:cc:from :subject:date:to:x-mailer; b=QC70fVjFD1DQAEVvUYWNAfAB0CEFIgs/sbpWX5QlAQIXZDyN4vQH7DD7Qc3qnTJS+7 x4AA8h5D/TLNoKu5iC2D1i7xZNVkP/piqW4A9bOxyw+Oo1Xt9o9FQLZO1c5i9dWSa8i0 hgpkm8gDpt2a5k4hB2pe2vdbMQGLy46czHEcw=
Received: by 10.115.134.11 with SMTP id l11mr8461685wan.160.1274349605688; Thu, 20 May 2010 03:00:05 -0700 (PDT)
Received: from [192.168.1.40] (207-118-26-12.dyn.centurytel.net [207.118.26.12]) by mx.google.com with ESMTPS id n29sm75916170wae.16.2010.05.20.03.00.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 20 May 2010 03:00:04 -0700 (PDT)
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com> <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com> <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com>
In-Reply-To: <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: multipart/alternative; boundary=Apple-Mail-1--310387461
Message-Id: <632C4898-F7DD-4B76-AAFB-D675346E2521@gmail.com>
From: Han Sontse <han.sontse.sl@gmail.com>
Date: Thu, 20 May 2010 02:59:15 -0700
To: Morgaine <morgaine.dinova@googlemail.com>
X-Mailer: Apple Mail (2.1078)
Cc: vwrap@ietf.org
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 10:00:18 -0000

--Apple-Mail-1--310387461
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

It's a bad idea to use IP addresses for anything other than addressing a =
machine level interface.  Using them to interface objects at or above =
the application level is asking for trouble.   UUIDs are UUIDs... IP =
addresses are IP addresses.   The two should not be mixed.   I recognize =
that it is temping to take advantage of the huge address space that IPv6 =
offers but my test engineer instincts tell me it is unwise to do so.

Han.
On May 20, 2010, at 2:50 AM, Morgaine wrote:

> A /64 is the smallest routable IPv6 subnet, hence there is no extra =
routing overhead for the 2^(128-64) addresses in the basic block that =
every user will have allocated.
>=20
> Needless to say, there won't be anything like 2^64 objects in your =
scenegraph, so if you use your IPv6 address space to address every =
scenegraph object that you have instantiated client-side, you will still =
have an extremely sparsely used /64 block.  You'll be keeping track of =
which addresses you have assigned dynamically of course. (An address =
space of this size is not linearly scannable in realistic time.)
>=20
> In principle this is no different to using UUIDs --- your IPv6 =
micro-servers will have unguessable IPv6 addresses within your /64 =
block, and it'll be up to you to tell other participants in the protocol =
(for example server-side objects) with which of your IPv6 micro-servers =
they are to communicate.  This is why an ADT that is supportive of IPv6 =
operation needs to be able to carry such data efficiently --- the UUID =
is no longer the only 128-bit datum of interest.
>=20
> Of course your entire /64 block is routed as one, since there are no =
smaller routable subnets in IPv6, and therefore your objections about =
routing non-scalability do not apply.
>=20
>=20
> Morgaine.
>=20
>=20
>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> On Wed, May 19, 2010 at 10:56 PM, Richard Barnes <rbarnes@bbn.com> =
wrote:
> The impact of IPv6 on VWs should be far less than you imagine, I =
think. :)
>=20
> It has often been said that many, many things will be assigned IPv6 =
addresses.  There will certainly be enough to go around, but that =
doesn't make them good application-layer identifiers.  If you want to =
use IP addresses with IP, they have to route, and that means that they =
have to be either (1) topologically assigned, or (2) overlay routed, =
e.g., with mobile IP.  So if you want to use an IP address to address =
something, you're going to have to either change that address when the =
thing gets connected differently, or you'll need some overlay routing =
scheme to route to a persistent address.  (And if you're not going to =
use the address with IP, then why would you use an IP address?)
>=20
> VWRAP, as an application layer protocol, has a choice about what =
identifiers to use for things and how to use those identifiers.  ISTM =
that using IP addresses (again, of either type) remains a bad idea, =
compared with something that is decoupled from the routing layer.
>=20
> As far as the DNS, I'm not sure what your point is:
> (i) DNS caching has been around for decades
> (ii) DNS names can already refer to multiple addresses
> (iii) Depends on implementation.  Maybe there's some application-layer =
way to resolve names.  E.g., SIP endpoints don't need to have DNS =
records because the INVITE transaction maps from SIP URIs to IP =
addresses.
> (iv) =46rom RFC 4291: "IPv6 addresses are 128-bit identifiers for =
interfaces and sets of
> interfaces"
> (v) Seems like there's a use case lurking, hard to address without =
details.  But you're probably still at the application layer.  For =
instance, if you were telling your peer to send you an HTTP request, you =
would send an HTTP URI, which can already handle IPv6 addresses.
>=20
> --Richard
>=20
>=20
>=20
> On May 19, 2010, at 9:35 AM, Morgaine wrote:
>=20
> The impact of IPv6 on VWs is going to be far greater than you imagine, =
I believe.  As things stand, VWRAP is being designed around the features =
and limitations of IPv4 networking.  It will of course be able to ride =
on top of IPv6 as a transport, but unable to benefit from its improved =
feature set, unless we provide the means to do so.
>=20
> The question "Why is there ever a need to carry an IP address in this =
application-layer protocol, as opposed to, say, a DNS name or a URI?" =
suggests an IPv4 mindset, because in IPv6 it has a variety of possible =
answers:  (i) When the DNS lookup has already been done and does not =
need to be done again, (ii) When a FQDN maps to multiple addresses, but =
you want to refer to a specific one, (iii) When an IPv6 address does not =
have an external address record, (iv) When the host is already known and =
the IP address denotes something other than a physical NIC interface, or =
(v) When listeners are allocated locally and dynamically for the current =
session only, and their IP addresses need to be communicated to a peer =
--- this will be an extremely common use case with IPv6.
>=20
> In today's IPv4-based systems, it is normal for a user's machine to =
have a single IP address, and for a client on that machine to talk to a =
server that has a single customer-facing IP address too (although it may =
also have others that are not public).  In IPv6-based systems, this =
simple scenario is still possible but represents only a special case =
among a new and vastly expanded set of IPv6 use cases.
>=20
> The smallest allocatable block of IPv6 address space is a /64, so =
2^(128-64) IP addresses is the number that most normal IPv6 users will =
have, although the much larger /48 blocks of 2^80 addresses are commonly =
assigned to users as well.  With such IP riches client-side, it is =
certain that they will be used for something, and the obvious suggestion =
is to give every VW object an IPv6 address of its own.
>=20
> Lest we forget, one of the most important properties of the REST =
paradigm is addressability, but the benefits of high addressability go =
far beyond the Web.  This is a property that will become ubiquitous =
throughout networked computing with IPv6.  It's probably no exaggeration =
to say that *everything* will be getting its own IP address. :-)
>=20
> Faced with that future, it's a mistake to think in IPv4 terms and =
consider IPv6 addresses as merely denoting a host which can be obtained =
from its FQDN.  That's IPv4 thinking, and represents only a very basic =
use case for IPv6.  In more extended use cases, IPv6 addresses will =
become much more like active local UUIDs than like today's host IP =
addresses.  They will be used for inner-application addressing, for =
example to make every object in an application an addressable =
micro-server.
>=20
> VWRAP is being born into an IPv6 world, and it would be a mistake to =
hardwire IPv4 thinking into its design.  We continually refer to the =
need for extensibility and a desire to future-proof the protocol, but =
lip service is not enough.  Adding IPv6 addresses to the underlying ADT =
would provide a bare minimum level of thinking ahead to support VWRAP =
implementations that embrace large numbers of communicating objects.  (A =
generally extensible ADT would of course achieve the same thing, and =
more.)
>=20
>=20
> Morgaine.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> On Mon, May 17, 2010 at 3:50 PM, David W Levine <dwl@us.ibm.com> =
wrote:
>=20
>=20
> vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26 AM:
>=20
> > [image removed]
> >
> > Re: [vwrap] VWRAP and IPv6
> >
> > Richard Barnes
> >
> > to:
> >
> > Morgaine
> >
> > 05/17/2010 10:09 AM
> >
> > Sent by:
> >
> > vwrap-bounces@ietf.org
> >
> > Cc:
> >
> > vwrap
> >
> > In the spirit of good layering, it seems like we should be talking
> > about avoiding direct reliance on IP addresses instead of how we can
> > accommodate different addresses in the protocol.  Why is there ever =
a
> > need to carry an IP address in this application-layer protocol, as
> > opposed to, say, a DNS name or a URI?
> >
> > --Richard
> >
> +1
>=20
> We may from time to time have a IP address stuck in the form of a URI
> which has the dotted decimal form of an resource. The spec should make
> sure that form can be an IPV6 address, but that should be very =
straight
> forward.
>=20
> There may be some IPV6 features which eventually impact us at the =
protocol
> design level, but the entire VWRAP specification has been written in =
terms of
> URIs and Capabilities, not in terms of low level IP addresses. It =
would take an
> incredibly powerful argument to suggest that this should change. =
Likewise, while
> IPV6 changes addressing at the bottom of the stack, it doesn't =
appreciably change
> the cost of holding open sessions, of managing sockets and buffers =
inside of
> clients (especially lightweight devices) Further while we can all =
devoutly hope
> that IPV6 finally deploys broadly, making it a dependancy in the near =
term feels
> rather like a roadblock to possible adoption.
>=20
> - David
> ~ Zha
>=20
>=20
>=20
> >
> > On May 14, 2010, at 7:32 AM, Morgaine wrote:
> >
> > > Despite exceedingly low takeup of IPv6 so far, it's coming, and in
> > > the context of IETF WG rates of progress, it is really imminent.  =
Of
> > > special relevance to us is that IPv4 addresses are projected to =
run
> > > out within roughly the same time frame as VWRAP materializes.
> > >
> > > There is little point in creating a new VW protocol today purely =
in
> > > the context of IPv4 without thinking about tomorrow's IPv6
> > > environment.  By the time that VWRAP is fully defined, we should
> > > expect a substantial and rapidly increasing proportion of VWRAP
> > > implementations to occur in IPv6-accessible worlds.  This is a
> > > situation for which we need to plan now, otherwise the protocol =
will
> > > be obsolete before it's even ready.
> > >
> > > To get the ball rolling, here are a few IPv6-related issues that =
we
> > > could usefully address in the group:
> > >
> > >    =95 The 128-bit IP address of IPv6 is likely to become a common
> > > payload, so it should be supported natively.  LLSD already =
supports
> > > one 128-bit data type of course, the UUID.  IPv6 addresses should
> > > not be transported in UUID fields however, since their statistical
> > > properties and semantics are totally different.  In any case, the
> > > two spaces are disjoint so confusing them would be a mistake.  The
> > > IPv6 address seems a good candidate for its own defined type, in =
the
> > > absence of wide integers.
> > >    =95 The extremely large address space of IPv6 has often been
> > > portrayed as allowing everything around us to have its own IP
> > > address.  In the context of virtual worlds, this idea can actually
> > > be put to good use, with each virtual object bearing its own IPv6
> > > address.  One candidate application for this has already been
> > > described in earlier discussions --- for example, implementing
> > > virtual object simulation in two parts, one client-side and one
> > > world-side, the two parts communicating directly.  IPv6 addressing
> > > of objects makes this relatively easy to achieve efficiently, so =
its
> > > implementation in IPv6-based worlds is almost inevitable before
> > > long.  VWRAP should be ready for this.
> > >    =95 The event queue in current implementations provides an =
indirect
> > > and highly inefficient way of achieving world-to-client
> > > communications.  IPv6 offers opportunities for direct =
communication
> > > that can make the event queue approach obsolete, so it's worth
> > > examining IPv6-oriented alternatives.
> > >    =95 We recently discussed feature and protocol negotiation =
within
> > > VWRAP.  IPv6 provides much opportunity for new features and =
protocol
> > > pathways to be negotiated between endpoints, so it gives us a very
> > > real and imminent set of use cases for negotiation.
> > >
> > > It would also be a feather in VWRAP's cap to be considered an =
"IPv6-
> > > capable application protocol" in a stronger sense than just to be
> > > carried by IPv6 networks.  IPv6 does after all bring new abilities
> > > to the table, such as the huge addressing, and it would be a =
mistake
> > > to ignore them.
> > >
> > >
> > > Morgaine.
> > >
> > >
> > >
> > > _______________________________________________
> > > vwrap mailing list
> > > vwrap@ietf.org
> > > https://www.ietf.org/mailman/listinfo/vwrap
> >
> > _______________________________________________
> > vwrap mailing list
> > vwrap@ietf.org
> > https://www.ietf.org/mailman/listinfo/vwrap
>=20
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>=20
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>=20
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap


--Apple-Mail-1--310387461
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">It's =
a bad idea to use IP addresses for anything other than addressing a =
machine level interface. &nbsp;Using them to interface objects at or =
above the application level is asking for trouble. &nbsp; UUIDs are =
UUIDs... IP addresses are IP addresses. &nbsp; The two should not be =
mixed. &nbsp; I recognize that it is temping to take advantage of the =
huge address space that IPv6 offers but my test engineer instincts tell =
me it is unwise to do so.<div><br></div><div>Han.<br><div><div>On May =
20, 2010, at 2:50 AM, Morgaine wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">A /64 is =
the smallest routable IPv6 subnet, hence there is no extra routing =
overhead for the 2^(128-64) addresses in the basic block that every user =
will have allocated.<br><br>Needless to say, there won't be anything =
like 2^64 objects in your scenegraph, so if you use your IPv6 address =
space to address every scenegraph object that you have instantiated =
client-side, you will still have an extremely sparsely used /64 =
block.&nbsp; You'll be keeping track of which addresses you have =
assigned dynamically of course. (An address space of this size is not =
linearly scannable in realistic time.)<br>
<br>In principle this is no different to using UUIDs --- your IPv6 =
micro-servers will have unguessable IPv6 addresses within your /64 =
block, and it'll be up to you to tell other participants in the protocol =
(for example server-side objects) with which of your IPv6 micro-servers =
they are to communicate.&nbsp; This is why an ADT that is supportive of =
IPv6 operation needs to be able to carry such data efficiently --- the =
UUID is no longer the only 128-bit datum of interest.<br>
<br>Of course your entire /64 block is routed as one, since there are no =
smaller routable subnets in IPv6, and therefore your objections about =
routing non-scalability do not =
apply.<br><br><br>Morgaine.<br><br><br><br><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br><div class=3D"gmail_quote">On =
Wed, May 19, 2010 at 10:56 PM, Richard Barnes <span dir=3D"ltr">&lt;<a =
href=3D"mailto:rbarnes@bbn.com">rbarnes@bbn.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"border-left: 1px =
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: =
1ex;">
The impact of IPv6 on VWs should be far less than you imagine, I think. =
:)<br>
<br>
It has often been said that many, many things will be assigned IPv6 =
addresses. &nbsp;There will certainly be enough to go around, but that =
doesn't make them good application-layer identifiers. &nbsp;If you want =
to use IP addresses with IP, they have to route, and that means that =
they have to be either (1) topologically assigned, or (2) overlay =
routed, e.g., with mobile IP. &nbsp;So if you want to use an IP address =
to address something, you're going to have to either change that address =
when the thing gets connected differently, or you'll need some overlay =
routing scheme to route to a persistent address. &nbsp;(And if you're =
not going to use the address with IP, then why would you use an IP =
address?)<br>

<br>
VWRAP, as an application layer protocol, has a choice about what =
identifiers to use for things and how to use those identifiers. =
&nbsp;ISTM that using IP addresses (again, of either type) remains a bad =
idea, compared with something that is decoupled from the routing =
layer.<br>

<br>
As far as the DNS, I'm not sure what your point is:<br>
(i) DNS caching has been around for decades<br>
(ii) DNS names can already refer to multiple addresses<br>
(iii) Depends on implementation. &nbsp;Maybe there's some =
application-layer way to resolve names. &nbsp;E.g., SIP endpoints don't =
need to have DNS records because the INVITE transaction maps from SIP =
URIs to IP addresses.<br>

(iv) =46rom RFC 4291: "IPv6 addresses are 128-bit identifiers for =
interfaces and sets of<br>
interfaces"<br>
(v) Seems like there's a use case lurking, hard to address without =
details. &nbsp;But you're probably still at the application layer. =
&nbsp;For instance, if you were telling your peer to send you an HTTP =
request, you would send an HTTP URI, which can already handle IPv6 =
addresses.<br>
<font color=3D"#888888">
<br>
--Richard</font><div><div></div><div class=3D"h5"><br>
<br>
<br>
On May 19, 2010, at 9:35 AM, Morgaine wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid =
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The impact of IPv6 on VWs is going to be far greater than you imagine, I =
believe. &nbsp;As things stand, VWRAP is being designed around the =
features and limitations of IPv4 networking. &nbsp;It will of course be =
able to ride on top of IPv6 as a transport, but unable to benefit from =
its improved feature set, unless we provide the means to do so.<br>

<br>
The question "Why is there ever a need to carry an IP address in this =
application-layer protocol, as opposed to, say, a DNS name or a URI?" =
suggests an IPv4 mindset, because in IPv6 it has a variety of possible =
answers: &nbsp;(i) When the DNS lookup has already been done and does =
not need to be done again, (ii) When a FQDN maps to multiple addresses, =
but you want to refer to a specific one, (iii) When an IPv6 address does =
not have an external address record, (iv) When the host is already known =
and the IP address denotes something other than a physical NIC =
interface, or (v) When listeners are allocated locally and dynamically =
for the current session only, and their IP addresses need to be =
communicated to a peer --- this will be an extremely common use case =
with IPv6.<br>

<br>
In today's IPv4-based systems, it is normal for a user's machine to have =
a single IP address, and for a client on that machine to talk to a =
server that has a single customer-facing IP address too (although it may =
also have others that are not public). &nbsp;In IPv6-based systems, this =
simple scenario is still possible but represents only a special case =
among a new and vastly expanded set of IPv6 use cases.<br>

<br>
The smallest allocatable block of IPv6 address space is a /64, so =
2^(128-64) IP addresses is the number that most normal IPv6 users will =
have, although the much larger /48 blocks of 2^80 addresses are commonly =
assigned to users as well. &nbsp;With such IP riches client-side, it is =
certain that they will be used for something, and the obvious suggestion =
is to give every VW object an IPv6 address of its own.<br>

<br>
Lest we forget, one of the most important properties of the REST =
paradigm is addressability, but the benefits of high addressability go =
far beyond the Web. &nbsp;This is a property that will become ubiquitous =
throughout networked computing with IPv6. &nbsp;It's probably no =
exaggeration to say that *everything* will be getting its own IP =
address. :-)<br>

<br>
Faced with that future, it's a mistake to think in IPv4 terms and =
consider IPv6 addresses as merely denoting a host which can be obtained =
from its FQDN. &nbsp;That's IPv4 thinking, and represents only a very =
basic use case for IPv6. &nbsp;In more extended use cases, IPv6 =
addresses will become much more like active local UUIDs than like =
today's host IP addresses. &nbsp;They will be used for inner-application =
addressing, for example to make every object in an application an =
addressable micro-server.<br>

<br>
VWRAP is being born into an IPv6 world, and it would be a mistake to =
hardwire IPv4 thinking into its design. &nbsp;We continually refer to =
the need for extensibility and a desire to future-proof the protocol, =
but lip service is not enough. &nbsp;Adding IPv6 addresses to the =
underlying ADT would provide a bare minimum level of thinking ahead to =
support VWRAP implementations that embrace large numbers of =
communicating objects. &nbsp;(A generally extensible ADT would of course =
achieve the same thing, and more.)<br>

<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
On Mon, May 17, 2010 at 3:50 PM, David W Levine &lt;<a =
href=3D"mailto:dwl@us.ibm.com" target=3D"_blank">dwl@us.ibm.com</a>&gt; =
wrote:<br>
<br>
<br>
<a href=3D"mailto:vwrap-bounces@ietf.org" =
target=3D"_blank">vwrap-bounces@ietf.org</a> wrote on 05/17/2010 =
10:08:26 AM:<br>
<br>
&gt; [image removed]<br>
&gt;<br>
&gt; Re: [vwrap] VWRAP and IPv6<br>
&gt;<br>
&gt; Richard Barnes<br>
&gt;<br>
&gt; to:<br>
&gt;<br>
&gt; Morgaine<br>
&gt;<br>
&gt; 05/17/2010 10:09 AM<br>
&gt;<br>
&gt; Sent by:<br>
&gt;<br>
&gt; <a href=3D"mailto:vwrap-bounces@ietf.org" =
target=3D"_blank">vwrap-bounces@ietf.org</a><br>
&gt;<br>
&gt; Cc:<br>
&gt;<br>
&gt; vwrap<br>
&gt;<br>
&gt; In the spirit of good layering, it seems like we should be =
talking<br>
&gt; about avoiding direct reliance on IP addresses instead of how we =
can<br>
&gt; accommodate different addresses in the protocol. &nbsp;Why is there =
ever a<br>
&gt; need to carry an IP address in this application-layer protocol, =
as<br>
&gt; opposed to, say, a DNS name or a URI?<br>
&gt;<br>
&gt; --Richard<br>
&gt;<br>
+1<br>
<br>
We may from time to time have a IP address stuck in the form of a =
URI<br>
which has the dotted decimal form of an resource. The spec should =
make<br>
sure that form can be an IPV6 address, but that should be very =
straight<br>
forward.<br>
<br>
There may be some IPV6 features which eventually impact us at the =
protocol<br>
design level, but the entire VWRAP specification has been written in =
terms of<br>
URIs and Capabilities, not in terms of low level IP addresses. It would =
take an<br>
incredibly powerful argument to suggest that this should change. =
Likewise, while<br>
IPV6 changes addressing at the bottom of the stack, it doesn't =
appreciably change<br>
the cost of holding open sessions, of managing sockets and buffers =
inside of<br>
clients (especially lightweight devices) Further while we can all =
devoutly hope<br>
that IPV6 finally deploys broadly, making it a dependancy in the near =
term feels<br>
rather like a roadblock to possible adoption.<br>
<br>
- David<br>
~ Zha<br>
<br>
<br>
<br>
&gt;<br>
&gt; On May 14, 2010, at 7:32 AM, Morgaine wrote:<br>
&gt;<br>
&gt; &gt; Despite exceedingly low takeup of IPv6 so far, it's coming, =
and in<br>
&gt; &gt; the context of IETF WG rates of progress, it is really =
imminent. &nbsp;Of<br>
&gt; &gt; special relevance to us is that IPv4 addresses are projected =
to run<br>
&gt; &gt; out within roughly the same time frame as VWRAP =
materializes.<br>
&gt; &gt;<br>
&gt; &gt; There is little point in creating a new VW protocol today =
purely in<br>
&gt; &gt; the context of IPv4 without thinking about tomorrow's IPv6<br>
&gt; &gt; environment. &nbsp;By the time that VWRAP is fully defined, we =
should<br>
&gt; &gt; expect a substantial and rapidly increasing proportion of =
VWRAP<br>
&gt; &gt; implementations to occur in IPv6-accessible worlds. &nbsp;This =
is a<br>
&gt; &gt; situation for which we need to plan now, otherwise the =
protocol will<br>
&gt; &gt; be obsolete before it's even ready.<br>
&gt; &gt;<br>
&gt; &gt; To get the ball rolling, here are a few IPv6-related issues =
that we<br>
&gt; &gt; could usefully address in the group:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp;=95 The 128-bit IP address of IPv6 is likely to =
become a common<br>
&gt; &gt; payload, so it should be supported natively. &nbsp;LLSD =
already supports<br>
&gt; &gt; one 128-bit data type of course, the UUID. &nbsp;IPv6 =
addresses should<br>
&gt; &gt; not be transported in UUID fields however, since their =
statistical<br>
&gt; &gt; properties and semantics are totally different. &nbsp;In any =
case, the<br>
&gt; &gt; two spaces are disjoint so confusing them would be a mistake. =
&nbsp;The<br>
&gt; &gt; IPv6 address seems a good candidate for its own defined type, =
in the<br>
&gt; &gt; absence of wide integers.<br>
&gt; &gt; &nbsp; &nbsp;=95 The extremely large address space of IPv6 has =
often been<br>
&gt; &gt; portrayed as allowing everything around us to have its own =
IP<br>
&gt; &gt; address. &nbsp;In the context of virtual worlds, this idea can =
actually<br>
&gt; &gt; be put to good use, with each virtual object bearing its own =
IPv6<br>
&gt; &gt; address. &nbsp;One candidate application for this has already =
been<br>
&gt; &gt; described in earlier discussions --- for example, =
implementing<br>
&gt; &gt; virtual object simulation in two parts, one client-side and =
one<br>
&gt; &gt; world-side, the two parts communicating directly. &nbsp;IPv6 =
addressing<br>
&gt; &gt; of objects makes this relatively easy to achieve efficiently, =
so its<br>
&gt; &gt; implementation in IPv6-based worlds is almost inevitable =
before<br>
&gt; &gt; long. &nbsp;VWRAP should be ready for this.<br>
&gt; &gt; &nbsp; &nbsp;=95 The event queue in current implementations =
provides an indirect<br>
&gt; &gt; and highly inefficient way of achieving world-to-client<br>
&gt; &gt; communications. &nbsp;IPv6 offers opportunities for direct =
communication<br>
&gt; &gt; that can make the event queue approach obsolete, so it's =
worth<br>
&gt; &gt; examining IPv6-oriented alternatives.<br>
&gt; &gt; &nbsp; &nbsp;=95 We recently discussed feature and protocol =
negotiation within<br>
&gt; &gt; VWRAP. &nbsp;IPv6 provides much opportunity for new features =
and protocol<br>
&gt; &gt; pathways to be negotiated between endpoints, so it gives us a =
very<br>
&gt; &gt; real and imminent set of use cases for negotiation.<br>
&gt; &gt;<br>
&gt; &gt; It would also be a feather in VWRAP's cap to be considered an =
"IPv6-<br>
&gt; &gt; capable application protocol" in a stronger sense than just to =
be<br>
&gt; &gt; carried by IPv6 networks. &nbsp;IPv6 does after all bring new =
abilities<br>
&gt; &gt; to the table, such as the huge addressing, and it would be a =
mistake<br>
&gt; &gt; to ignore them.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Morgaine.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; vwrap mailing list<br>
&gt; &gt; <a href=3D"mailto:vwrap@ietf.org" =
target=3D"_blank">vwrap@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; vwrap mailing list<br>
&gt; <a href=3D"mailto:vwrap@ietf.org" =
target=3D"_blank">vwrap@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>=

<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
</blockquote>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>=

<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
</div></div></blockquote></div><br>
_______________________________________________<br>vwrap mailing =
list<br><a =
href=3D"mailto:vwrap@ietf.org">vwrap@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/vwrap<br></blockquote></div><br></div></body></html>=

--Apple-Mail-1--310387461--

From mike.dickson@hp.com  Thu May 20 05:55:20 2010
Return-Path: <mike.dickson@hp.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 433B43A6BE5 for <vwrap@core3.amsl.com>; Thu, 20 May 2010 05:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.999
X-Spam-Level: 
X-Spam-Status: No, score=-103.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 LrO-AU9T+Vri for <vwrap@core3.amsl.com>; Thu, 20 May 2010 05:55:18 -0700 (PDT)
Received: from g4t0016.houston.hp.com (g4t0016.houston.hp.com [15.201.24.19]) by core3.amsl.com (Postfix) with ESMTP id 59EF43A6BD8 for <vwrap@ietf.org>; Thu, 20 May 2010 05:55:18 -0700 (PDT)
Received: from g5t0012.atlanta.hp.com (g5t0012.atlanta.hp.com [15.192.0.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by g4t0016.houston.hp.com (Postfix) with ESMTPS id 0402714479; Thu, 20 May 2010 12:55:11 +0000 (UTC)
Received: from [192.168.1.139] (conr-adsl-209-169-125-189.consolidated.net [209.169.125.189]) by g5t0012.atlanta.hp.com (Postfix) with ESMTPSA id 48F0210003; Thu, 20 May 2010 12:55:10 +0000 (UTC)
From: Michael Dickson <mike.dickson@hp.com>
To: Morgaine <morgaine.dinova@googlemail.com>
In-Reply-To: <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com>
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com> <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com> <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 20 May 2010 07:55:08 -0500
Message-ID: <1274360108.2087.37.camel@mdickson-laptop.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
Cc: "vwrap@ietf.org" <vwrap@ietf.org>
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 12:55:20 -0000

On Thu, 2010-05-20 at 09:50 +0000, Morgaine wrote:
> A /64 is the smallest routable IPv6 subnet, hence there is no extra
> routing overhead for the 2^(128-64) addresses in the basic block that
> every user will have allocated.
> 
> Needless to say, there won't be anything like 2^64 objects in your
> scenegraph, so if you use your IPv6 address space to address every
> scenegraph object that you have instantiated client-side, you will
> still have an extremely sparsely used /64 block.  You'll be keeping
> track of which addresses you have assigned dynamically of course. (An
> address space of this size is not linearly scannable in realistic
> time.)
> 
> In principle this is no different to using UUIDs --- your IPv6
> micro-servers will have unguessable IPv6 addresses within your /64
> block, and it'll be up to you to tell other participants in the
> protocol (for example server-side objects) with which of your IPv6
> micro-servers they are to communicate.  This is why an ADT that is
> supportive of IPv6 operation needs to be able to carry such data
> efficiently --- the UUID is no longer the only 128-bit datum of
> interest.

No, it *is* different as another poster has indicated because a hardware
or software layer needs to maintain the physical to address translation
and those tables are generally of finite size. In a virtualized
environment it gets worse size across multiple vm's you may need to
maintain more that one copy for each entry to get hardware speeds.

VWRAP is an application layer protocol and as such it should use logical
names for things as opposed to IP addresses and let the appropriate name
to address translation happen.

-1 to using IPv6 addresses as identifiers for this and other reasons
that have been raised. I think the consensus has been pretty solidly
against it so far.

Mike


> Of course your entire /64 block is routed as one, since there are no
> smaller routable subnets in IPv6, and therefore your objections about
> routing non-scalability do not apply.
> 
> 
> Morgaine.
> 
> 
> 
> 
> =====================================
> 
> On Wed, May 19, 2010 at 10:56 PM, Richard Barnes <rbarnes@bbn.com>
> wrote:
>         The impact of IPv6 on VWs should be far less than you imagine,
>         I think. :)
>         
>         It has often been said that many, many things will be assigned
>         IPv6 addresses.  There will certainly be enough to go around,
>         but that doesn't make them good application-layer
>         identifiers.  If you want to use IP addresses with IP, they
>         have to route, and that means that they have to be either (1)
>         topologically assigned, or (2) overlay routed, e.g., with
>         mobile IP.  So if you want to use an IP address to address
>         something, you're going to have to either change that address
>         when the thing gets connected differently, or you'll need some
>         overlay routing scheme to route to a persistent address.  (And
>         if you're not going to use the address with IP, then why would
>         you use an IP address?)
>         
>         VWRAP, as an application layer protocol, has a choice about
>         what identifiers to use for things and how to use those
>         identifiers.  ISTM that using IP addresses (again, of either
>         type) remains a bad idea, compared with something that is
>         decoupled from the routing layer.
>         
>         As far as the DNS, I'm not sure what your point is:
>         (i) DNS caching has been around for decades
>         (ii) DNS names can already refer to multiple addresses
>         (iii) Depends on implementation.  Maybe there's some
>         application-layer way to resolve names.  E.g., SIP endpoints
>         don't need to have DNS records because the INVITE transaction
>         maps from SIP URIs to IP addresses.
>         (iv) From RFC 4291: "IPv6 addresses are 128-bit identifiers
>         for interfaces and sets of
>         interfaces"
>         (v) Seems like there's a use case lurking, hard to address
>         without details.  But you're probably still at the application
>         layer.  For instance, if you were telling your peer to send
>         you an HTTP request, you would send an HTTP URI, which can
>         already handle IPv6 addresses.
>         
>         --Richard
>         
>         
>         
>         
>         On May 19, 2010, at 9:35 AM, Morgaine wrote:
>         
>                 The impact of IPv6 on VWs is going to be far greater
>                 than you imagine, I believe.  As things stand, VWRAP
>                 is being designed around the features and limitations
>                 of IPv4 networking.  It will of course be able to ride
>                 on top of IPv6 as a transport, but unable to benefit
>                 from its improved feature set, unless we provide the
>                 means to do so.
>                 
>                 The question "Why is there ever a need to carry an IP
>                 address in this application-layer protocol, as opposed
>                 to, say, a DNS name or a URI?" suggests an IPv4
>                 mindset, because in IPv6 it has a variety of possible
>                 answers:  (i) When the DNS lookup has already been
>                 done and does not need to be done again, (ii) When a
>                 FQDN maps to multiple addresses, but you want to refer
>                 to a specific one, (iii) When an IPv6 address does not
>                 have an external address record, (iv) When the host is
>                 already known and the IP address denotes something
>                 other than a physical NIC interface, or (v) When
>                 listeners are allocated locally and dynamically for
>                 the current session only, and their IP addresses need
>                 to be communicated to a peer --- this will be an
>                 extremely common use case with IPv6.
>                 
>                 In today's IPv4-based systems, it is normal for a
>                 user's machine to have a single IP address, and for a
>                 client on that machine to talk to a server that has a
>                 single customer-facing IP address too (although it may
>                 also have others that are not public).  In IPv6-based
>                 systems, this simple scenario is still possible but
>                 represents only a special case among a new and vastly
>                 expanded set of IPv6 use cases.
>                 
>                 The smallest allocatable block of IPv6 address space
>                 is a /64, so 2^(128-64) IP addresses is the number
>                 that most normal IPv6 users will have, although the
>                 much larger /48 blocks of 2^80 addresses are commonly
>                 assigned to users as well.  With such IP riches
>                 client-side, it is certain that they will be used for
>                 something, and the obvious suggestion is to give every
>                 VW object an IPv6 address of its own.
>                 
>                 Lest we forget, one of the most important properties
>                 of the REST paradigm is addressability, but the
>                 benefits of high addressability go far beyond the
>                 Web.  This is a property that will become ubiquitous
>                 throughout networked computing with IPv6.  It's
>                 probably no exaggeration to say that *everything* will
>                 be getting its own IP address. :-)
>                 
>                 Faced with that future, it's a mistake to think in
>                 IPv4 terms and consider IPv6 addresses as merely
>                 denoting a host which can be obtained from its FQDN.
>                  That's IPv4 thinking, and represents only a very
>                 basic use case for IPv6.  In more extended use cases,
>                 IPv6 addresses will become much more like active local
>                 UUIDs than like today's host IP addresses.  They will
>                 be used for inner-application addressing, for example
>                 to make every object in an application an addressable
>                 micro-server.
>                 
>                 VWRAP is being born into an IPv6 world, and it would
>                 be a mistake to hardwire IPv4 thinking into its
>                 design.  We continually refer to the need for
>                 extensibility and a desire to future-proof the
>                 protocol, but lip service is not enough.  Adding IPv6
>                 addresses to the underlying ADT would provide a bare
>                 minimum level of thinking ahead to support VWRAP
>                 implementations that embrace large numbers of
>                 communicating objects.  (A generally extensible ADT
>                 would of course achieve the same thing, and more.)
>                 
>                 
>                 Morgaine.
>                 
>                 
>                 
>                 
>                 
>                 
>                 
>                 ==============================================
>                 
>                 On Mon, May 17, 2010 at 3:50 PM, David W Levine
>                 <dwl@us.ibm.com> wrote:
>                 
>                 
>                 vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26
>                 AM:
>                 
>                 > [image removed]
>                 >
>                 > Re: [vwrap] VWRAP and IPv6
>                 >
>                 > Richard Barnes
>                 >
>                 > to:
>                 >
>                 > Morgaine
>                 >
>                 > 05/17/2010 10:09 AM
>                 >
>                 > Sent by:
>                 >
>                 > vwrap-bounces@ietf.org
>                 >
>                 > Cc:
>                 >
>                 > vwrap
>                 >
>                 > In the spirit of good layering, it seems like we
>                 should be talking
>                 > about avoiding direct reliance on IP addresses
>                 instead of how we can
>                 > accommodate different addresses in the protocol.
>                  Why is there ever a
>                 > need to carry an IP address in this
>                 application-layer protocol, as
>                 > opposed to, say, a DNS name or a URI?
>                 >
>                 > --Richard
>                 >
>                 +1
>                 
>                 We may from time to time have a IP address stuck in
>                 the form of a URI
>                 which has the dotted decimal form of an resource. The
>                 spec should make
>                 sure that form can be an IPV6 address, but that should
>                 be very straight
>                 forward.
>                 
>                 There may be some IPV6 features which eventually
>                 impact us at the protocol
>                 design level, but the entire VWRAP specification has
>                 been written in terms of
>                 URIs and Capabilities, not in terms of low level IP
>                 addresses. It would take an
>                 incredibly powerful argument to suggest that this
>                 should change. Likewise, while
>                 IPV6 changes addressing at the bottom of the stack, it
>                 doesn't appreciably change
>                 the cost of holding open sessions, of managing sockets
>                 and buffers inside of
>                 clients (especially lightweight devices) Further while
>                 we can all devoutly hope
>                 that IPV6 finally deploys broadly, making it a
>                 dependancy in the near term feels
>                 rather like a roadblock to possible adoption.
>                 
>                 - David
>                 ~ Zha
>                 
>                 
>                 
>                 >
>                 > On May 14, 2010, at 7:32 AM, Morgaine wrote:
>                 >
>                 > > Despite exceedingly low takeup of IPv6 so far,
>                 it's coming, and in
>                 > > the context of IETF WG rates of progress, it is
>                 really imminent.  Of
>                 > > special relevance to us is that IPv4 addresses are
>                 projected to run
>                 > > out within roughly the same time frame as VWRAP
>                 materializes.
>                 > >
>                 > > There is little point in creating a new VW
>                 protocol today purely in
>                 > > the context of IPv4 without thinking about
>                 tomorrow's IPv6
>                 > > environment.  By the time that VWRAP is fully
>                 defined, we should
>                 > > expect a substantial and rapidly increasing
>                 proportion of VWRAP
>                 > > implementations to occur in IPv6-accessible
>                 worlds.  This is a
>                 > > situation for which we need to plan now, otherwise
>                 the protocol will
>                 > > be obsolete before it's even ready.
>                 > >
>                 > > To get the ball rolling, here are a few
>                 IPv6-related issues that we
>                 > > could usefully address in the group:
>                 > >
>                 > >    • The 128-bit IP address of IPv6 is likely to
>                 become a common
>                 > > payload, so it should be supported natively.  LLSD
>                 already supports
>                 > > one 128-bit data type of course, the UUID.  IPv6
>                 addresses should
>                 > > not be transported in UUID fields however, since
>                 their statistical
>                 > > properties and semantics are totally different.
>                  In any case, the
>                 > > two spaces are disjoint so confusing them would be
>                 a mistake.  The
>                 > > IPv6 address seems a good candidate for its own
>                 defined type, in the
>                 > > absence of wide integers.
>                 > >    • The extremely large address space of IPv6 has
>                 often been
>                 > > portrayed as allowing everything around us to have
>                 its own IP
>                 > > address.  In the context of virtual worlds, this
>                 idea can actually
>                 > > be put to good use, with each virtual object
>                 bearing its own IPv6
>                 > > address.  One candidate application for this has
>                 already been
>                 > > described in earlier discussions --- for example,
>                 implementing
>                 > > virtual object simulation in two parts, one
>                 client-side and one
>                 > > world-side, the two parts communicating directly.
>                  IPv6 addressing
>                 > > of objects makes this relatively easy to achieve
>                 efficiently, so its
>                 > > implementation in IPv6-based worlds is almost
>                 inevitable before
>                 > > long.  VWRAP should be ready for this.
>                 > >    • The event queue in current implementations
>                 provides an indirect
>                 > > and highly inefficient way of achieving
>                 world-to-client
>                 > > communications.  IPv6 offers opportunities for
>                 direct communication
>                 > > that can make the event queue approach obsolete,
>                 so it's worth
>                 > > examining IPv6-oriented alternatives.
>                 > >    • We recently discussed feature and protocol
>                 negotiation within
>                 > > VWRAP.  IPv6 provides much opportunity for new
>                 features and protocol
>                 > > pathways to be negotiated between endpoints, so it
>                 gives us a very
>                 > > real and imminent set of use cases for
>                 negotiation.
>                 > >
>                 > > It would also be a feather in VWRAP's cap to be
>                 considered an "IPv6-
>                 > > capable application protocol" in a stronger sense
>                 than just to be
>                 > > carried by IPv6 networks.  IPv6 does after all
>                 bring new abilities
>                 > > to the table, such as the huge addressing, and it
>                 would be a mistake
>                 > > to ignore them.
>                 > >
>                 > >
>                 > > Morgaine.
>                 > >
>                 > >
>                 > >
>                 > > _______________________________________________
>                 > > vwrap mailing list
>                 > > vwrap@ietf.org
>                 > > https://www.ietf.org/mailman/listinfo/vwrap
>                 >
>                 > _______________________________________________
>                 > vwrap mailing list
>                 > vwrap@ietf.org
>                 > https://www.ietf.org/mailman/listinfo/vwrap
>                 
>                 _______________________________________________
>                 vwrap mailing list
>                 vwrap@ietf.org
>                 https://www.ietf.org/mailman/listinfo/vwrap
>         
>         _______________________________________________
>         vwrap mailing list
>         vwrap@ietf.org
>         https://www.ietf.org/mailman/listinfo/vwrap
>         
> 



From rbarnes@bbn.com  Thu May 20 06:19:56 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 071E83A69CC for <vwrap@core3.amsl.com>; Thu, 20 May 2010 06:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.596
X-Spam-Level: 
X-Spam-Status: No, score=-0.596 tagged_above=-999 required=5 tests=[AWL=-0.597, BAYES_50=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 7UvYyT5tpAB2 for <vwrap@core3.amsl.com>; Thu, 20 May 2010 06:19:50 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 7E3A63A6C1F for <vwrap@ietf.org>; Thu, 20 May 2010 06:18:34 -0700 (PDT)
Received: from [128.89.255.32] (port=56245 helo=[192.168.1.46]) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OF5dp-0007lM-Hw; Thu, 20 May 2010 09:18:27 -0400
Message-Id: <F8868B50-7B53-4E1A-9F5F-E6FA2933F269@bbn.com>
From: Richard Barnes <rbarnes@bbn.com>
To: Michael Dickson <mike.dickson@hp.com>
In-Reply-To: <1274360108.2087.37.camel@mdickson-laptop.local>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 20 May 2010 09:18:23 -0400
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com> <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com> <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com> <1274360108.2087.37.camel@mdickson-laptop.local>
X-Mailer: Apple Mail (2.936)
Cc: "vwrap@ietf.org" <vwrap@ietf.org>
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 13:19:56 -0000

Just to try to clarify the pain that comes from trying to use IPv6 =20
addresses as pure identifiers (as separate from their routing/locator =20=

function), I can think of at least five groups who are trying to come =20=

up with approaches to making this work:
1. HIP <http://tools.ietf.org/wg/hip/>
2. HIPRG <http://irtf.org/charter?gtype=3Drg&group=3Dhiprg>
3. MIP6 <http://tools.ietf.org/wg/mip6/>
4. LISP <http://tools.ietf.org/wg/lisp/>
5. MEXT < http://tools.ietf.org/wg/mext/>

--Richard



On May 20, 2010, at 8:55 AM, Michael Dickson wrote:

> On Thu, 2010-05-20 at 09:50 +0000, Morgaine wrote:
>> A /64 is the smallest routable IPv6 subnet, hence there is no extra
>> routing overhead for the 2^(128-64) addresses in the basic block that
>> every user will have allocated.
>>
>> Needless to say, there won't be anything like 2^64 objects in your
>> scenegraph, so if you use your IPv6 address space to address every
>> scenegraph object that you have instantiated client-side, you will
>> still have an extremely sparsely used /64 block.  You'll be keeping
>> track of which addresses you have assigned dynamically of course. (An
>> address space of this size is not linearly scannable in realistic
>> time.)
>>
>> In principle this is no different to using UUIDs --- your IPv6
>> micro-servers will have unguessable IPv6 addresses within your /64
>> block, and it'll be up to you to tell other participants in the
>> protocol (for example server-side objects) with which of your IPv6
>> micro-servers they are to communicate.  This is why an ADT that is
>> supportive of IPv6 operation needs to be able to carry such data
>> efficiently --- the UUID is no longer the only 128-bit datum of
>> interest.
>
> No, it *is* different as another poster has indicated because a =20
> hardware
> or software layer needs to maintain the physical to address =20
> translation
> and those tables are generally of finite size. In a virtualized
> environment it gets worse size across multiple vm's you may need to
> maintain more that one copy for each entry to get hardware speeds.
>
> VWRAP is an application layer protocol and as such it should use =20
> logical
> names for things as opposed to IP addresses and let the appropriate =20=

> name
> to address translation happen.
>
> -1 to using IPv6 addresses as identifiers for this and other reasons
> that have been raised. I think the consensus has been pretty solidly
> against it so far.
>
> Mike
>
>
>> Of course your entire /64 block is routed as one, since there are no
>> smaller routable subnets in IPv6, and therefore your objections about
>> routing non-scalability do not apply.
>>
>>
>> Morgaine.
>>
>>
>>
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> On Wed, May 19, 2010 at 10:56 PM, Richard Barnes <rbarnes@bbn.com>
>> wrote:
>>        The impact of IPv6 on VWs should be far less than you imagine,
>>        I think. :)
>>
>>        It has often been said that many, many things will be assigned
>>        IPv6 addresses.  There will certainly be enough to go around,
>>        but that doesn't make them good application-layer
>>        identifiers.  If you want to use IP addresses with IP, they
>>        have to route, and that means that they have to be either (1)
>>        topologically assigned, or (2) overlay routed, e.g., with
>>        mobile IP.  So if you want to use an IP address to address
>>        something, you're going to have to either change that address
>>        when the thing gets connected differently, or you'll need some
>>        overlay routing scheme to route to a persistent address.  (And
>>        if you're not going to use the address with IP, then why would
>>        you use an IP address?)
>>
>>        VWRAP, as an application layer protocol, has a choice about
>>        what identifiers to use for things and how to use those
>>        identifiers.  ISTM that using IP addresses (again, of either
>>        type) remains a bad idea, compared with something that is
>>        decoupled from the routing layer.
>>
>>        As far as the DNS, I'm not sure what your point is:
>>        (i) DNS caching has been around for decades
>>        (ii) DNS names can already refer to multiple addresses
>>        (iii) Depends on implementation.  Maybe there's some
>>        application-layer way to resolve names.  E.g., SIP endpoints
>>        don't need to have DNS records because the INVITE transaction
>>        maps from SIP URIs to IP addresses.
>>        (iv) =46rom RFC 4291: "IPv6 addresses are 128-bit identifiers
>>        for interfaces and sets of
>>        interfaces"
>>        (v) Seems like there's a use case lurking, hard to address
>>        without details.  But you're probably still at the application
>>        layer.  For instance, if you were telling your peer to send
>>        you an HTTP request, you would send an HTTP URI, which can
>>        already handle IPv6 addresses.
>>
>>        --Richard
>>
>>
>>
>>
>>        On May 19, 2010, at 9:35 AM, Morgaine wrote:
>>
>>                The impact of IPv6 on VWs is going to be far greater
>>                than you imagine, I believe.  As things stand, VWRAP
>>                is being designed around the features and limitations
>>                of IPv4 networking.  It will of course be able to ride
>>                on top of IPv6 as a transport, but unable to benefit
>>                from its improved feature set, unless we provide the
>>                means to do so.
>>
>>                The question "Why is there ever a need to carry an IP
>>                address in this application-layer protocol, as opposed
>>                to, say, a DNS name or a URI?" suggests an IPv4
>>                mindset, because in IPv6 it has a variety of possible
>>                answers:  (i) When the DNS lookup has already been
>>                done and does not need to be done again, (ii) When a
>>                FQDN maps to multiple addresses, but you want to refer
>>                to a specific one, (iii) When an IPv6 address does not
>>                have an external address record, (iv) When the host is
>>                already known and the IP address denotes something
>>                other than a physical NIC interface, or (v) When
>>                listeners are allocated locally and dynamically for
>>                the current session only, and their IP addresses need
>>                to be communicated to a peer --- this will be an
>>                extremely common use case with IPv6.
>>
>>                In today's IPv4-based systems, it is normal for a
>>                user's machine to have a single IP address, and for a
>>                client on that machine to talk to a server that has a
>>                single customer-facing IP address too (although it may
>>                also have others that are not public).  In IPv6-based
>>                systems, this simple scenario is still possible but
>>                represents only a special case among a new and vastly
>>                expanded set of IPv6 use cases.
>>
>>                The smallest allocatable block of IPv6 address space
>>                is a /64, so 2^(128-64) IP addresses is the number
>>                that most normal IPv6 users will have, although the
>>                much larger /48 blocks of 2^80 addresses are commonly
>>                assigned to users as well.  With such IP riches
>>                client-side, it is certain that they will be used for
>>                something, and the obvious suggestion is to give every
>>                VW object an IPv6 address of its own.
>>
>>                Lest we forget, one of the most important properties
>>                of the REST paradigm is addressability, but the
>>                benefits of high addressability go far beyond the
>>                Web.  This is a property that will become ubiquitous
>>                throughout networked computing with IPv6.  It's
>>                probably no exaggeration to say that *everything* will
>>                be getting its own IP address. :-)
>>
>>                Faced with that future, it's a mistake to think in
>>                IPv4 terms and consider IPv6 addresses as merely
>>                denoting a host which can be obtained from its FQDN.
>>                 That's IPv4 thinking, and represents only a very
>>                basic use case for IPv6.  In more extended use cases,
>>                IPv6 addresses will become much more like active local
>>                UUIDs than like today's host IP addresses.  They will
>>                be used for inner-application addressing, for example
>>                to make every object in an application an addressable
>>                micro-server.
>>
>>                VWRAP is being born into an IPv6 world, and it would
>>                be a mistake to hardwire IPv4 thinking into its
>>                design.  We continually refer to the need for
>>                extensibility and a desire to future-proof the
>>                protocol, but lip service is not enough.  Adding IPv6
>>                addresses to the underlying ADT would provide a bare
>>                minimum level of thinking ahead to support VWRAP
>>                implementations that embrace large numbers of
>>                communicating objects.  (A generally extensible ADT
>>                would of course achieve the same thing, and more.)
>>
>>
>>                Morgaine.
>>
>>
>>
>>
>>
>>
>>
>>                =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
>>
>>                On Mon, May 17, 2010 at 3:50 PM, David W Levine
>>                <dwl@us.ibm.com> wrote:
>>
>>
>>                vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26
>>                AM:
>>
>>> [image removed]
>>>
>>> Re: [vwrap] VWRAP and IPv6
>>>
>>> Richard Barnes
>>>
>>> to:
>>>
>>> Morgaine
>>>
>>> 05/17/2010 10:09 AM
>>>
>>> Sent by:
>>>
>>> vwrap-bounces@ietf.org
>>>
>>> Cc:
>>>
>>> vwrap
>>>
>>> In the spirit of good layering, it seems like we
>>                should be talking
>>> about avoiding direct reliance on IP addresses
>>                instead of how we can
>>> accommodate different addresses in the protocol.
>>                 Why is there ever a
>>> need to carry an IP address in this
>>                application-layer protocol, as
>>> opposed to, say, a DNS name or a URI?
>>>
>>> --Richard
>>>
>>                +1
>>
>>                We may from time to time have a IP address stuck in
>>                the form of a URI
>>                which has the dotted decimal form of an resource. The
>>                spec should make
>>                sure that form can be an IPV6 address, but that should
>>                be very straight
>>                forward.
>>
>>                There may be some IPV6 features which eventually
>>                impact us at the protocol
>>                design level, but the entire VWRAP specification has
>>                been written in terms of
>>                URIs and Capabilities, not in terms of low level IP
>>                addresses. It would take an
>>                incredibly powerful argument to suggest that this
>>                should change. Likewise, while
>>                IPV6 changes addressing at the bottom of the stack, it
>>                doesn't appreciably change
>>                the cost of holding open sessions, of managing sockets
>>                and buffers inside of
>>                clients (especially lightweight devices) Further while
>>                we can all devoutly hope
>>                that IPV6 finally deploys broadly, making it a
>>                dependancy in the near term feels
>>                rather like a roadblock to possible adoption.
>>
>>                - David
>>                ~ Zha
>>
>>
>>
>>>
>>> On May 14, 2010, at 7:32 AM, Morgaine wrote:
>>>
>>>> Despite exceedingly low takeup of IPv6 so far,
>>                it's coming, and in
>>>> the context of IETF WG rates of progress, it is
>>                really imminent.  Of
>>>> special relevance to us is that IPv4 addresses are
>>                projected to run
>>>> out within roughly the same time frame as VWRAP
>>                materializes.
>>>>
>>>> There is little point in creating a new VW
>>                protocol today purely in
>>>> the context of IPv4 without thinking about
>>                tomorrow's IPv6
>>>> environment.  By the time that VWRAP is fully
>>                defined, we should
>>>> expect a substantial and rapidly increasing
>>                proportion of VWRAP
>>>> implementations to occur in IPv6-accessible
>>                worlds.  This is a
>>>> situation for which we need to plan now, otherwise
>>                the protocol will
>>>> be obsolete before it's even ready.
>>>>
>>>> To get the ball rolling, here are a few
>>                IPv6-related issues that we
>>>> could usefully address in the group:
>>>>
>>>>   =95 The 128-bit IP address of IPv6 is likely to
>>                become a common
>>>> payload, so it should be supported natively.  LLSD
>>                already supports
>>>> one 128-bit data type of course, the UUID.  IPv6
>>                addresses should
>>>> not be transported in UUID fields however, since
>>                their statistical
>>>> properties and semantics are totally different.
>>                 In any case, the
>>>> two spaces are disjoint so confusing them would be
>>                a mistake.  The
>>>> IPv6 address seems a good candidate for its own
>>                defined type, in the
>>>> absence of wide integers.
>>>>   =95 The extremely large address space of IPv6 has
>>                often been
>>>> portrayed as allowing everything around us to have
>>                its own IP
>>>> address.  In the context of virtual worlds, this
>>                idea can actually
>>>> be put to good use, with each virtual object
>>                bearing its own IPv6
>>>> address.  One candidate application for this has
>>                already been
>>>> described in earlier discussions --- for example,
>>                implementing
>>>> virtual object simulation in two parts, one
>>                client-side and one
>>>> world-side, the two parts communicating directly.
>>                 IPv6 addressing
>>>> of objects makes this relatively easy to achieve
>>                efficiently, so its
>>>> implementation in IPv6-based worlds is almost
>>                inevitable before
>>>> long.  VWRAP should be ready for this.
>>>>   =95 The event queue in current implementations
>>                provides an indirect
>>>> and highly inefficient way of achieving
>>                world-to-client
>>>> communications.  IPv6 offers opportunities for
>>                direct communication
>>>> that can make the event queue approach obsolete,
>>                so it's worth
>>>> examining IPv6-oriented alternatives.
>>>>   =95 We recently discussed feature and protocol
>>                negotiation within
>>>> VWRAP.  IPv6 provides much opportunity for new
>>                features and protocol
>>>> pathways to be negotiated between endpoints, so it
>>                gives us a very
>>>> real and imminent set of use cases for
>>                negotiation.
>>>>
>>>> It would also be a feather in VWRAP's cap to be
>>                considered an "IPv6-
>>>> capable application protocol" in a stronger sense
>>                than just to be
>>>> carried by IPv6 networks.  IPv6 does after all
>>                bring new abilities
>>>> to the table, such as the huge addressing, and it
>>                would be a mistake
>>>> to ignore them.
>>>>
>>>>
>>>> Morgaine.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> vwrap mailing list
>>>> vwrap@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/vwrap
>>>
>>> _______________________________________________
>>> vwrap mailing list
>>> vwrap@ietf.org
>>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>>                _______________________________________________
>>                vwrap mailing list
>>                vwrap@ietf.org
>>                https://www.ietf.org/mailman/listinfo/vwrap
>>
>>        _______________________________________________
>>        vwrap mailing list
>>        vwrap@ietf.org
>>        https://www.ietf.org/mailman/listinfo/vwrap
>>
>>
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap


From morgaine.dinova@googlemail.com  Thu May 20 06:28:27 2010
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 663EC3A6D4D for <vwrap@core3.amsl.com>; Thu, 20 May 2010 06:28:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.825
X-Spam-Level: 
X-Spam-Status: No, score=0.825 tagged_above=-999 required=5 tests=[AWL=0.201,  BAYES_50=0.001, 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 Oe-DGk8ONfLY for <vwrap@core3.amsl.com>; Thu, 20 May 2010 06:28:23 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id EBE2A3A6D48 for <vwrap@ietf.org>; Thu, 20 May 2010 06:23:48 -0700 (PDT)
Received: by wwb24 with SMTP id 24so1515275wwb.31 for <vwrap@ietf.org>; Thu, 20 May 2010 06:23:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=MnwUkvhCjm+Ah04avzFFCI5Wi5IVXM2TQJrd6hlzkYI=; b=Ez6WH0WSJy489N18xwhjkA/Zxlm/oHY2EIt/RSkMnY5hG2ciwtXS3kYrVzYo//Aoi7 +bGRniCq5H2cRuJTBzy4yuit8A6Nem97pbxwZtRqA4Wpsk9YkwuWiphF8ciHdKY/gReo JF8JdpbS/WHRXQws0dMTDaO8Ji7oJq83CmTyU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KHWXiulwuI4Z1TV8tWdZqQd5WGM/EwiR4gcj0OhPOCvw7k/pToTb8XTfd2P3pvX1Dl gfQrVwpAhHX+n3fko32x+E4Tg9BbLbmLdD6CuDKtTle7wNnJtGkXIE8XHjp8rnoj6bUk W3XPP4iL8BR2GDtl0f6aPdbQ2RojiWDzkd40g=
MIME-Version: 1.0
Received: by 10.216.174.142 with SMTP id x14mr1510331wel.8.1274361813996; Thu,  20 May 2010 06:23:33 -0700 (PDT)
Received: by 10.216.26.132 with HTTP; Thu, 20 May 2010 06:23:33 -0700 (PDT)
In-Reply-To: <632C4898-F7DD-4B76-AAFB-D675346E2521@gmail.com>
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com> <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com> <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com> <632C4898-F7DD-4B76-AAFB-D675346E2521@gmail.com>
Date: Thu, 20 May 2010 14:23:33 +0100
Message-ID: <AANLkTik42H1xhnr_yljo06-4thbaT3GcLBDabzoj2c2t@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary=0016e6541d883d15590487067b03
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 13:28:27 -0000

--0016e6541d883d15590487067b03
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Thu, May 20, 2010 at 10:59 AM, Han Sontse <han.sontse.sl@gmail.com>wrote=
:

> I recognize that it is temping to take advantage of the huge address spac=
e
> that IPv6 offers but my *test engineer instincts* tell me it is unwise to
> do so.
>


I too am an engineer, but solid engineering instincts do not tell us to use
only those facilities whose numbers or sizes can be tested exhaustively.  I=
f
it were so, we would not have multi-terabyte disk drives today.

The /64 minimum routable subnet of IPv6 address space was not designed as i=
t
was because people were expected to need 2^64 NIC cards in their PCs.  This
immense per-user address block was created because IPv6 designers could see
beyond IPv4's use of addresses for host interface identification, and were
visionary enough to realize that all objects could benefit from network
addressability.  This also happens to be one of the key messages of REST.
Addressability is extremely important, the finer the better, not only on th=
e
Web, and not only with URIs.

With IPv6 just around the corner, I foresee such addressability at fine
levels of granularity appearing in VWs relatively soon.  IPv4 worlds will
have to emulate what IPv6 worlds achieve natively, and that is the right wa=
y
around.  When legacy design restricts progress, the only thing it achieves
is rapid obsolescence.

I would prefer VWRAP not to be painting itself into an IPv4 corner of
obsolescence before it's even released, which is why I'm raising this topic
--- it's intended as a heads-up for the group.

Since the rise of VWs and IPv6 take-up are going to occur concurrently, I
think the next few years are going to be very interesting on the VW
networking front.  My recommendation is to observe carefully what happens,
and not to make any rash decisions based on legacy ideas that could cut off
your future.


Morgaine.





=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On Thu, May 20, 2010 at 10:59 AM, Han Sontse <han.sontse.sl@gmail.com>wrote=
:

> It's a bad idea to use IP addresses for anything other than addressing a
> machine level interface.  Using them to interface objects at or above the
> application level is asking for trouble.   UUIDs are UUIDs... IP addresse=
s
> are IP addresses.   The two should not be mixed.   I recognize that it is
> temping to take advantage of the huge address space that IPv6 offers but =
my
> test engineer instincts tell me it is unwise to do so.
>
> Han.
>
> On May 20, 2010, at 2:50 AM, Morgaine wrote:
>
> A /64 is the smallest routable IPv6 subnet, hence there is no extra routi=
ng
> overhead for the 2^(128-64) addresses in the basic block that every user
> will have allocated.
>
> Needless to say, there won't be anything like 2^64 objects in your
> scenegraph, so if you use your IPv6 address space to address every
> scenegraph object that you have instantiated client-side, you will still
> have an extremely sparsely used /64 block.  You'll be keeping track of wh=
ich
> addresses you have assigned dynamically of course. (An address space of t=
his
> size is not linearly scannable in realistic time.)
>
> In principle this is no different to using UUIDs --- your IPv6
> micro-servers will have unguessable IPv6 addresses within your /64 block,
> and it'll be up to you to tell other participants in the protocol (for
> example server-side objects) with which of your IPv6 micro-servers they a=
re
> to communicate.  This is why an ADT that is supportive of IPv6 operation
> needs to be able to carry such data efficiently --- the UUID is no longer
> the only 128-bit datum of interest.
>
> Of course your entire /64 block is routed as one, since there are no
> smaller routable subnets in IPv6, and therefore your objections about
> routing non-scalability do not apply.
>
>
> Morgaine.
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> On Wed, May 19, 2010 at 10:56 PM, Richard Barnes <rbarnes@bbn.com> wrote:
>
>> The impact of IPv6 on VWs should be far less than you imagine, I think. =
:)
>>
>> It has often been said that many, many things will be assigned IPv6
>> addresses.  There will certainly be enough to go around, but that doesn'=
t
>> make them good application-layer identifiers.  If you want to use IP
>> addresses with IP, they have to route, and that means that they have to =
be
>> either (1) topologically assigned, or (2) overlay routed, e.g., with mob=
ile
>> IP.  So if you want to use an IP address to address something, you're go=
ing
>> to have to either change that address when the thing gets connected
>> differently, or you'll need some overlay routing scheme to route to a
>> persistent address.  (And if you're not going to use the address with IP=
,
>> then why would you use an IP address?)
>>
>> VWRAP, as an application layer protocol, has a choice about what
>> identifiers to use for things and how to use those identifiers.  ISTM th=
at
>> using IP addresses (again, of either type) remains a bad idea, compared =
with
>> something that is decoupled from the routing layer.
>>
>> As far as the DNS, I'm not sure what your point is:
>> (i) DNS caching has been around for decades
>> (ii) DNS names can already refer to multiple addresses
>> (iii) Depends on implementation.  Maybe there's some application-layer w=
ay
>> to resolve names.  E.g., SIP endpoints don't need to have DNS records
>> because the INVITE transaction maps from SIP URIs to IP addresses.
>> (iv) From RFC 4291: "IPv6 addresses are 128-bit identifiers for interfac=
es
>> and sets of
>> interfaces"
>> (v) Seems like there's a use case lurking, hard to address without
>> details.  But you're probably still at the application layer.  For insta=
nce,
>> if you were telling your peer to send you an HTTP request, you would sen=
d an
>> HTTP URI, which can already handle IPv6 addresses.
>>
>> --Richard
>>
>>
>>
>> On May 19, 2010, at 9:35 AM, Morgaine wrote:
>>
>>  The impact of IPv6 on VWs is going to be far greater than you imagine, =
I
>>> believe.  As things stand, VWRAP is being designed around the features =
and
>>> limitations of IPv4 networking.  It will of course be able to ride on t=
op of
>>> IPv6 as a transport, but unable to benefit from its improved feature se=
t,
>>> unless we provide the means to do so.
>>>
>>> The question "Why is there ever a need to carry an IP address in this
>>> application-layer protocol, as opposed to, say, a DNS name or a URI?"
>>> suggests an IPv4 mindset, because in IPv6 it has a variety of possible
>>> answers:  (i) When the DNS lookup has already been done and does not ne=
ed to
>>> be done again, (ii) When a FQDN maps to multiple addresses, but you wan=
t to
>>> refer to a specific one, (iii) When an IPv6 address does not have an
>>> external address record, (iv) When the host is already known and the IP
>>> address denotes something other than a physical NIC interface, or (v) W=
hen
>>> listeners are allocated locally and dynamically for the current session
>>> only, and their IP addresses need to be communicated to a peer --- this=
 will
>>> be an extremely common use case with IPv6.
>>>
>>> In today's IPv4-based systems, it is normal for a user's machine to hav=
e
>>> a single IP address, and for a client on that machine to talk to a serv=
er
>>> that has a single customer-facing IP address too (although it may also =
have
>>> others that are not public).  In IPv6-based systems, this simple scenar=
io is
>>> still possible but represents only a special case among a new and vastl=
y
>>> expanded set of IPv6 use cases.
>>>
>>> The smallest allocatable block of IPv6 address space is a /64, so
>>> 2^(128-64) IP addresses is the number that most normal IPv6 users will =
have,
>>> although the much larger /48 blocks of 2^80 addresses are commonly assi=
gned
>>> to users as well.  With such IP riches client-side, it is certain that =
they
>>> will be used for something, and the obvious suggestion is to give every=
 VW
>>> object an IPv6 address of its own.
>>>
>>> Lest we forget, one of the most important properties of the REST paradi=
gm
>>> is addressability, but the benefits of high addressability go far beyon=
d the
>>> Web.  This is a property that will become ubiquitous throughout network=
ed
>>> computing with IPv6.  It's probably no exaggeration to say that *everyt=
hing*
>>> will be getting its own IP address. :-)
>>>
>>> Faced with that future, it's a mistake to think in IPv4 terms and
>>> consider IPv6 addresses as merely denoting a host which can be obtained=
 from
>>> its FQDN.  That's IPv4 thinking, and represents only a very basic use c=
ase
>>> for IPv6.  In more extended use cases, IPv6 addresses will become much =
more
>>> like active local UUIDs than like today's host IP addresses.  They will=
 be
>>> used for inner-application addressing, for example to make every object=
 in
>>> an application an addressable micro-server.
>>>
>>> VWRAP is being born into an IPv6 world, and it would be a mistake to
>>> hardwire IPv4 thinking into its design.  We continually refer to the ne=
ed
>>> for extensibility and a desire to future-proof the protocol, but lip se=
rvice
>>> is not enough.  Adding IPv6 addresses to the underlying ADT would provi=
de a
>>> bare minimum level of thinking ahead to support VWRAP implementations t=
hat
>>> embrace large numbers of communicating objects.  (A generally extensibl=
e ADT
>>> would of course achieve the same thing, and more.)
>>>
>>>
>>> Morgaine.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>
>>> On Mon, May 17, 2010 at 3:50 PM, David W Levine <dwl@us.ibm.com> wrote:
>>>
>>>
>>> vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26 AM:
>>>
>>> > [image removed]
>>> >
>>> > Re: [vwrap] VWRAP and IPv6
>>> >
>>> > Richard Barnes
>>> >
>>> > to:
>>> >
>>> > Morgaine
>>> >
>>> > 05/17/2010 10:09 AM
>>> >
>>> > Sent by:
>>> >
>>> > vwrap-bounces@ietf.org
>>> >
>>> > Cc:
>>> >
>>> > vwrap
>>> >
>>> > In the spirit of good layering, it seems like we should be talking
>>> > about avoiding direct reliance on IP addresses instead of how we can
>>> > accommodate different addresses in the protocol.  Why is there ever a
>>> > need to carry an IP address in this application-layer protocol, as
>>> > opposed to, say, a DNS name or a URI?
>>> >
>>> > --Richard
>>> >
>>> +1
>>>
>>> We may from time to time have a IP address stuck in the form of a URI
>>> which has the dotted decimal form of an resource. The spec should make
>>> sure that form can be an IPV6 address, but that should be very straight
>>> forward.
>>>
>>> There may be some IPV6 features which eventually impact us at the
>>> protocol
>>> design level, but the entire VWRAP specification has been written in
>>> terms of
>>> URIs and Capabilities, not in terms of low level IP addresses. It would
>>> take an
>>> incredibly powerful argument to suggest that this should change.
>>> Likewise, while
>>> IPV6 changes addressing at the bottom of the stack, it doesn't
>>> appreciably change
>>> the cost of holding open sessions, of managing sockets and buffers insi=
de
>>> of
>>> clients (especially lightweight devices) Further while we can all
>>> devoutly hope
>>> that IPV6 finally deploys broadly, making it a dependancy in the near
>>> term feels
>>> rather like a roadblock to possible adoption.
>>>
>>> - David
>>> ~ Zha
>>>
>>>
>>>
>>> >
>>> > On May 14, 2010, at 7:32 AM, Morgaine wrote:
>>> >
>>> > > Despite exceedingly low takeup of IPv6 so far, it's coming, and in
>>> > > the context of IETF WG rates of progress, it is really imminent.  O=
f
>>> > > special relevance to us is that IPv4 addresses are projected to run
>>> > > out within roughly the same time frame as VWRAP materializes.
>>> > >
>>> > > There is little point in creating a new VW protocol today purely in
>>> > > the context of IPv4 without thinking about tomorrow's IPv6
>>> > > environment.  By the time that VWRAP is fully defined, we should
>>> > > expect a substantial and rapidly increasing proportion of VWRAP
>>> > > implementations to occur in IPv6-accessible worlds.  This is a
>>> > > situation for which we need to plan now, otherwise the protocol wil=
l
>>> > > be obsolete before it's even ready.
>>> > >
>>> > > To get the ball rolling, here are a few IPv6-related issues that we
>>> > > could usefully address in the group:
>>> > >
>>> > >    =95 The 128-bit IP address of IPv6 is likely to become a common
>>> > > payload, so it should be supported natively.  LLSD already supports
>>> > > one 128-bit data type of course, the UUID.  IPv6 addresses should
>>> > > not be transported in UUID fields however, since their statistical
>>> > > properties and semantics are totally different.  In any case, the
>>> > > two spaces are disjoint so confusing them would be a mistake.  The
>>> > > IPv6 address seems a good candidate for its own defined type, in th=
e
>>> > > absence of wide integers.
>>> > >    =95 The extremely large address space of IPv6 has often been
>>> > > portrayed as allowing everything around us to have its own IP
>>> > > address.  In the context of virtual worlds, this idea can actually
>>> > > be put to good use, with each virtual object bearing its own IPv6
>>> > > address.  One candidate application for this has already been
>>> > > described in earlier discussions --- for example, implementing
>>> > > virtual object simulation in two parts, one client-side and one
>>> > > world-side, the two parts communicating directly.  IPv6 addressing
>>> > > of objects makes this relatively easy to achieve efficiently, so it=
s
>>> > > implementation in IPv6-based worlds is almost inevitable before
>>> > > long.  VWRAP should be ready for this.
>>> > >    =95 The event queue in current implementations provides an indir=
ect
>>> > > and highly inefficient way of achieving world-to-client
>>> > > communications.  IPv6 offers opportunities for direct communication
>>> > > that can make the event queue approach obsolete, so it's worth
>>> > > examining IPv6-oriented alternatives.
>>> > >    =95 We recently discussed feature and protocol negotiation withi=
n
>>> > > VWRAP.  IPv6 provides much opportunity for new features and protoco=
l
>>> > > pathways to be negotiated between endpoints, so it gives us a very
>>> > > real and imminent set of use cases for negotiation.
>>> > >
>>> > > It would also be a feather in VWRAP's cap to be considered an "IPv6=
-
>>> > > capable application protocol" in a stronger sense than just to be
>>> > > carried by IPv6 networks.  IPv6 does after all bring new abilities
>>> > > to the table, such as the huge addressing, and it would be a mistak=
e
>>> > > to ignore them.
>>> > >
>>> > >
>>> > > Morgaine.
>>> > >
>>> > >
>>> > >
>>> > > _______________________________________________
>>> > > vwrap mailing list
>>> > > vwrap@ietf.org
>>> > > https://www.ietf.org/mailman/listinfo/vwrap
>>> >
>>> > _______________________________________________
>>> > vwrap mailing list
>>> > vwrap@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/vwrap
>>>
>>> _______________________________________________
>>> vwrap mailing list
>>> vwrap@ietf.org
>>> https://www.ietf.org/mailman/listinfo/vwrap
>>>
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
>
>

--0016e6541d883d15590487067b03
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Thu, May 20, 2010 at 10:59 AM, Han Sontse <span dir=3D"ltr">&lt;<a href=
=3D"http://han.sontse.sl">han.sontse.sl</a>@<a href=3D"http://gmail.com">gm=
ail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padd=
ing-left: 1ex;">
<div style=3D"word-wrap: break-word;">I recognize that it is temping to tak=
e advantage of the huge address
space that IPv6 offers but my <b>test engineer instincts</b> tell me it is
unwise to do so.</div></blockquote><div><br><br>I too am an engineer, but s=
olid engineering instincts do not tell us to use only those facilities whos=
e numbers or sizes can be tested exhaustively.=A0 If it were so, we would n=
ot have multi-terabyte disk drives today.<br>
<br>The /64 minimum routable subnet of IPv6 address space was not designed =
as it was because people were expected to need 2^64 NIC cards in their PCs.=
=A0 This immense per-user address block was created because IPv6 designers =
could see beyond IPv4&#39;s use of addresses for host interface identificat=
ion, and were visionary enough to realize that all objects could benefit fr=
om network addressability.=A0 This also happens to be one of the key messag=
es of REST.=A0 Addressability is extremely important, the finer the better,=
 not only on the Web, and not only with URIs.<br>
</div><br>With IPv6 just around the corner, I foresee such addressability a=
t fine levels of granularity appearing in VWs relatively soon.=A0 IPv4 worl=
ds will have to emulate what IPv6 worlds achieve natively, and that is the =
right way around.=A0 When legacy design restricts progress, the only thing =
it achieves is rapid obsolescence.<br>
<br>I would prefer VWRAP not to be painting itself into an IPv4 corner of o=
bsolescence before it&#39;s even released, which is why I&#39;m raising thi=
s topic --- it&#39;s intended as a heads-up for the group.<br><br>Since the=
 rise of VWs and IPv6 take-up are going to occur concurrently, I think the =
next few years are going to be very interesting on the VW networking front.=
=A0 My recommendation is to observe carefully what happens, and not to make=
 any rash decisions based on legacy ideas that could cut off your future.<b=
r>
<br><br>Morgaine.<br><br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
><br><div class=3D"gmail_quote">On Thu, May 20, 2010 at 10:59 AM, Han Sonts=
e <span dir=3D"ltr">&lt;<a href=3D"http://han.sontse.sl">han.sontse.sl</a>@=
<a href=3D"http://gmail.com">gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=3D"wor=
d-wrap: break-word;">It&#39;s a bad idea to use IP addresses for anything o=
ther than addressing a machine level interface. =A0Using them to interface =
objects at or above the application level is asking for trouble. =A0 UUIDs =
are UUIDs... IP addresses are IP addresses. =A0 The two should not be mixed=
. =A0 I recognize that it is temping to take advantage of the huge address =
space that IPv6 offers but my test engineer instincts tell me it is unwise =
to do so.<div>
<br></div><div><font color=3D"#888888">Han.</font><div><div></div><div clas=
s=3D"h5"><br><div><div>On May 20, 2010, at 2:50 AM, Morgaine wrote:</div><b=
r><blockquote type=3D"cite">A /64 is the smallest routable IPv6 subnet, hen=
ce there is no extra routing overhead for the 2^(128-64) addresses in the b=
asic block that every user will have allocated.<br>
<br>Needless to say, there won&#39;t be anything like 2^64 objects in your =
scenegraph, so if you use your IPv6 address space to address every scenegra=
ph object that you have instantiated client-side, you will still have an ex=
tremely sparsely used /64 block.=A0 You&#39;ll be keeping track of which ad=
dresses you have assigned dynamically of course. (An address space of this =
size is not linearly scannable in realistic time.)<br>

<br>In principle this is no different to using UUIDs --- your IPv6 micro-se=
rvers will have unguessable IPv6 addresses within your /64 block, and it&#3=
9;ll be up to you to tell other participants in the protocol (for example s=
erver-side objects) with which of your IPv6 micro-servers they are to commu=
nicate.=A0 This is why an ADT that is supportive of IPv6 operation needs to=
 be able to carry such data efficiently --- the UUID is no longer the only =
128-bit datum of interest.<br>

<br>Of course your entire /64 block is routed as one, since there are no sm=
aller routable subnets in IPv6, and therefore your objections about routing=
 non-scalability do not apply.<br><br><br>Morgaine.<br><br><br><br><br>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br><div class=3D"gmail_quote">On W=
ed, May 19, 2010 at 10:56 PM, Richard Barnes <span dir=3D"ltr">&lt;<a href=
=3D"mailto:rbarnes@bbn.com" target=3D"_blank">rbarnes@bbn.com</a>&gt;</span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The impact of IPv6 on VWs should be far less than you imagine, I think. :)<=
br>
<br>
It has often been said that many, many things will be assigned IPv6 address=
es. =A0There will certainly be enough to go around, but that doesn&#39;t ma=
ke them good application-layer identifiers. =A0If you want to use IP addres=
ses with IP, they have to route, and that means that they have to be either=
 (1) topologically assigned, or (2) overlay routed, e.g., with mobile IP. =
=A0So if you want to use an IP address to address something, you&#39;re goi=
ng to have to either change that address when the thing gets connected diff=
erently, or you&#39;ll need some overlay routing scheme to route to a persi=
stent address. =A0(And if you&#39;re not going to use the address with IP, =
then why would you use an IP address?)<br>


<br>
VWRAP, as an application layer protocol, has a choice about what identifier=
s to use for things and how to use those identifiers. =A0ISTM that using IP=
 addresses (again, of either type) remains a bad idea, compared with someth=
ing that is decoupled from the routing layer.<br>


<br>
As far as the DNS, I&#39;m not sure what your point is:<br>
(i) DNS caching has been around for decades<br>
(ii) DNS names can already refer to multiple addresses<br>
(iii) Depends on implementation. =A0Maybe there&#39;s some application-laye=
r way to resolve names. =A0E.g., SIP endpoints don&#39;t need to have DNS r=
ecords because the INVITE transaction maps from SIP URIs to IP addresses.<b=
r>


(iv) From RFC 4291: &quot;IPv6 addresses are 128-bit identifiers for interf=
aces and sets of<br>
interfaces&quot;<br>
(v) Seems like there&#39;s a use case lurking, hard to address without deta=
ils. =A0But you&#39;re probably still at the application layer. =A0For inst=
ance, if you were telling your peer to send you an HTTP request, you would =
send an HTTP URI, which can already handle IPv6 addresses.<br>

<font color=3D"#888888">
<br>
--Richard</font><div><div></div><div><br>
<br>
<br>
On May 19, 2010, at 9:35 AM, Morgaine wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The impact of IPv6 on VWs is going to be far greater than you imagine, I be=
lieve. =A0As things stand, VWRAP is being designed around the features and =
limitations of IPv4 networking. =A0It will of course be able to ride on top=
 of IPv6 as a transport, but unable to benefit from its improved feature se=
t, unless we provide the means to do so.<br>


<br>
The question &quot;Why is there ever a need to carry an IP address in this =
application-layer protocol, as opposed to, say, a DNS name or a URI?&quot; =
suggests an IPv4 mindset, because in IPv6 it has a variety of possible answ=
ers: =A0(i) When the DNS lookup has already been done and does not need to =
be done again, (ii) When a FQDN maps to multiple addresses, but you want to=
 refer to a specific one, (iii) When an IPv6 address does not have an exter=
nal address record, (iv) When the host is already known and the IP address =
denotes something other than a physical NIC interface, or (v) When listener=
s are allocated locally and dynamically for the current session only, and t=
heir IP addresses need to be communicated to a peer --- this will be an ext=
remely common use case with IPv6.<br>


<br>
In today&#39;s IPv4-based systems, it is normal for a user&#39;s machine to=
 have a single IP address, and for a client on that machine to talk to a se=
rver that has a single customer-facing IP address too (although it may also=
 have others that are not public). =A0In IPv6-based systems, this simple sc=
enario is still possible but represents only a special case among a new and=
 vastly expanded set of IPv6 use cases.<br>


<br>
The smallest allocatable block of IPv6 address space is a /64, so 2^(128-64=
) IP addresses is the number that most normal IPv6 users will have, althoug=
h the much larger /48 blocks of 2^80 addresses are commonly assigned to use=
rs as well. =A0With such IP riches client-side, it is certain that they wil=
l be used for something, and the obvious suggestion is to give every VW obj=
ect an IPv6 address of its own.<br>


<br>
Lest we forget, one of the most important properties of the REST paradigm i=
s addressability, but the benefits of high addressability go far beyond the=
 Web. =A0This is a property that will become ubiquitous throughout networke=
d computing with IPv6. =A0It&#39;s probably no exaggeration to say that *ev=
erything* will be getting its own IP address. :-)<br>


<br>
Faced with that future, it&#39;s a mistake to think in IPv4 terms and consi=
der IPv6 addresses as merely denoting a host which can be obtained from its=
 FQDN. =A0That&#39;s IPv4 thinking, and represents only a very basic use ca=
se for IPv6. =A0In more extended use cases, IPv6 addresses will become much=
 more like active local UUIDs than like today&#39;s host IP addresses. =A0T=
hey will be used for inner-application addressing, for example to make ever=
y object in an application an addressable micro-server.<br>


<br>
VWRAP is being born into an IPv6 world, and it would be a mistake to hardwi=
re IPv4 thinking into its design. =A0We continually refer to the need for e=
xtensibility and a desire to future-proof the protocol, but lip service is =
not enough. =A0Adding IPv6 addresses to the underlying ADT would provide a =
bare minimum level of thinking ahead to support VWRAP implementations that =
embrace large numbers of communicating objects. =A0(A generally extensible =
ADT would of course achieve the same thing, and more.)<br>


<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
On Mon, May 17, 2010 at 3:50 PM, David W Levine &lt;<a href=3D"mailto:dwl@u=
s.ibm.com" target=3D"_blank">dwl@us.ibm.com</a>&gt; wrote:<br>
<br>
<br>
<a href=3D"mailto:vwrap-bounces@ietf.org" target=3D"_blank">vwrap-bounces@i=
etf.org</a> wrote on 05/17/2010 10:08:26 AM:<br>
<br>
&gt; [image removed]<br>
&gt;<br>
&gt; Re: [vwrap] VWRAP and IPv6<br>
&gt;<br>
&gt; Richard Barnes<br>
&gt;<br>
&gt; to:<br>
&gt;<br>
&gt; Morgaine<br>
&gt;<br>
&gt; 05/17/2010 10:09 AM<br>
&gt;<br>
&gt; Sent by:<br>
&gt;<br>
&gt; <a href=3D"mailto:vwrap-bounces@ietf.org" target=3D"_blank">vwrap-boun=
ces@ietf.org</a><br>
&gt;<br>
&gt; Cc:<br>
&gt;<br>
&gt; vwrap<br>
&gt;<br>
&gt; In the spirit of good layering, it seems like we should be talking<br>
&gt; about avoiding direct reliance on IP addresses instead of how we can<b=
r>
&gt; accommodate different addresses in the protocol. =A0Why is there ever =
a<br>
&gt; need to carry an IP address in this application-layer protocol, as<br>
&gt; opposed to, say, a DNS name or a URI?<br>
&gt;<br>
&gt; --Richard<br>
&gt;<br>
+1<br>
<br>
We may from time to time have a IP address stuck in the form of a URI<br>
which has the dotted decimal form of an resource. The spec should make<br>
sure that form can be an IPV6 address, but that should be very straight<br>
forward.<br>
<br>
There may be some IPV6 features which eventually impact us at the protocol<=
br>
design level, but the entire VWRAP specification has been written in terms =
of<br>
URIs and Capabilities, not in terms of low level IP addresses. It would tak=
e an<br>
incredibly powerful argument to suggest that this should change. Likewise, =
while<br>
IPV6 changes addressing at the bottom of the stack, it doesn&#39;t apprecia=
bly change<br>
the cost of holding open sessions, of managing sockets and buffers inside o=
f<br>
clients (especially lightweight devices) Further while we can all devoutly =
hope<br>
that IPV6 finally deploys broadly, making it a dependancy in the near term =
feels<br>
rather like a roadblock to possible adoption.<br>
<br>
- David<br>
~ Zha<br>
<br>
<br>
<br>
&gt;<br>
&gt; On May 14, 2010, at 7:32 AM, Morgaine wrote:<br>
&gt;<br>
&gt; &gt; Despite exceedingly low takeup of IPv6 so far, it&#39;s coming, a=
nd in<br>
&gt; &gt; the context of IETF WG rates of progress, it is really imminent. =
=A0Of<br>
&gt; &gt; special relevance to us is that IPv4 addresses are projected to r=
un<br>
&gt; &gt; out within roughly the same time frame as VWRAP materializes.<br>
&gt; &gt;<br>
&gt; &gt; There is little point in creating a new VW protocol today purely =
in<br>
&gt; &gt; the context of IPv4 without thinking about tomorrow&#39;s IPv6<br=
>
&gt; &gt; environment. =A0By the time that VWRAP is fully defined, we shoul=
d<br>
&gt; &gt; expect a substantial and rapidly increasing proportion of VWRAP<b=
r>
&gt; &gt; implementations to occur in IPv6-accessible worlds. =A0This is a<=
br>
&gt; &gt; situation for which we need to plan now, otherwise the protocol w=
ill<br>
&gt; &gt; be obsolete before it&#39;s even ready.<br>
&gt; &gt;<br>
&gt; &gt; To get the ball rolling, here are a few IPv6-related issues that =
we<br>
&gt; &gt; could usefully address in the group:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0=95 The 128-bit IP address of IPv6 is likely to become a c=
ommon<br>
&gt; &gt; payload, so it should be supported natively. =A0LLSD already supp=
orts<br>
&gt; &gt; one 128-bit data type of course, the UUID. =A0IPv6 addresses shou=
ld<br>
&gt; &gt; not be transported in UUID fields however, since their statistica=
l<br>
&gt; &gt; properties and semantics are totally different. =A0In any case, t=
he<br>
&gt; &gt; two spaces are disjoint so confusing them would be a mistake. =A0=
The<br>
&gt; &gt; IPv6 address seems a good candidate for its own defined type, in =
the<br>
&gt; &gt; absence of wide integers.<br>
&gt; &gt; =A0 =A0=95 The extremely large address space of IPv6 has often be=
en<br>
&gt; &gt; portrayed as allowing everything around us to have its own IP<br>
&gt; &gt; address. =A0In the context of virtual worlds, this idea can actua=
lly<br>
&gt; &gt; be put to good use, with each virtual object bearing its own IPv6=
<br>
&gt; &gt; address. =A0One candidate application for this has already been<b=
r>
&gt; &gt; described in earlier discussions --- for example, implementing<br=
>
&gt; &gt; virtual object simulation in two parts, one client-side and one<b=
r>
&gt; &gt; world-side, the two parts communicating directly. =A0IPv6 address=
ing<br>
&gt; &gt; of objects makes this relatively easy to achieve efficiently, so =
its<br>
&gt; &gt; implementation in IPv6-based worlds is almost inevitable before<b=
r>
&gt; &gt; long. =A0VWRAP should be ready for this.<br>
&gt; &gt; =A0 =A0=95 The event queue in current implementations provides an=
 indirect<br>
&gt; &gt; and highly inefficient way of achieving world-to-client<br>
&gt; &gt; communications. =A0IPv6 offers opportunities for direct communica=
tion<br>
&gt; &gt; that can make the event queue approach obsolete, so it&#39;s wort=
h<br>
&gt; &gt; examining IPv6-oriented alternatives.<br>
&gt; &gt; =A0 =A0=95 We recently discussed feature and protocol negotiation=
 within<br>
&gt; &gt; VWRAP. =A0IPv6 provides much opportunity for new features and pro=
tocol<br>
&gt; &gt; pathways to be negotiated between endpoints, so it gives us a ver=
y<br>
&gt; &gt; real and imminent set of use cases for negotiation.<br>
&gt; &gt;<br>
&gt; &gt; It would also be a feather in VWRAP&#39;s cap to be considered an=
 &quot;IPv6-<br>
&gt; &gt; capable application protocol&quot; in a stronger sense than just =
to be<br>
&gt; &gt; carried by IPv6 networks. =A0IPv6 does after all bring new abilit=
ies<br>
&gt; &gt; to the table, such as the huge addressing, and it would be a mist=
ake<br>
&gt; &gt; to ignore them.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Morgaine.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; vwrap mailing list<br>
&gt; &gt; <a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.or=
g</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D=
"_blank">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; vwrap mailing list<br>
&gt; <a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
</blockquote>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
</div></div></blockquote></div><br>
_______________________________________________<br>vwrap mailing list<br><a=
 href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">http=
s://www.ietf.org/mailman/listinfo/vwrap</a><br>
</blockquote></div><br></div></div></div></div></blockquote></div><br>

--0016e6541d883d15590487067b03--

From rbarnes@bbn.com  Thu May 20 06:43:41 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A54533A6AC4 for <vwrap@core3.amsl.com>; Thu, 20 May 2010 06:43:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.561
X-Spam-Level: 
X-Spam-Status: No, score=-0.561 tagged_above=-999 required=5 tests=[AWL=-0.562, BAYES_50=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 MS4fvLYyGo2q for <vwrap@core3.amsl.com>; Thu, 20 May 2010 06:43:39 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 9676E3A67F7 for <vwrap@ietf.org>; Thu, 20 May 2010 06:43:37 -0700 (PDT)
Received: from [128.89.255.32] (port=56541 helo=[192.168.1.46]) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OF625-0008D2-1s; Thu, 20 May 2010 09:43:30 -0400
Message-Id: <B2E410EF-1AD1-45E6-88A3-BE18FCC1571F@bbn.com>
From: Richard Barnes <rbarnes@bbn.com>
To: Morgaine <morgaine.dinova@googlemail.com>
In-Reply-To: <AANLkTik42H1xhnr_yljo06-4thbaT3GcLBDabzoj2c2t@mail.gmail.com>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 20 May 2010 09:43:28 -0400
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com> <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com> <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com> <632C4898-F7DD-4B76-AAFB-D675346E2521@gmail.com> <AANLkTik42H1xhnr_yljo06-4thbaT3GcLBDabzoj2c2t@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: vwrap@ietf.org
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 13:43:41 -0000

As an aside, there's nothing that says that subscribers have to be =20
allocated a /64.  Some proposed addressing schemes that are more =20
conservative (in the Asia/Pacific region IIRC) actually assign much =20
longer prefixes (smaller address blocks) to customers.

Fine-grained addressability is not the same as fine-grained allocation =20=

of *IP* addresses. Think of it this way: HTTP has very fine-grained =20
addressability, with individual identifier/locators for pages, images, =20=

scripts, etc.  It's able to accomplish this not by assigning an IPv6 =20
address to every object, but by using an application-layer identifier/=20=

locator -- namely a URL.

Not using IPv6 addresses in applications is not painting oneself into =20=

an IPv4 corner, it's good protocol design following the layering model =20=

of the Internet.  (If we're using IPv4 addresses for identifiers, we =20
shouldn't be doing that either!)  Abstracting over IP addresses is =20
about freeing the application from having to worry about whether its =20
IPv4 or IPv6 or IPv10 or X.25 or whatever else at the network layer.

--Richard



On May 20, 2010, at 9:23 AM, Morgaine wrote:

> On Thu, May 20, 2010 at 10:59 AM, Han Sontse =20
> <han.sontse.sl@gmail.com> wrote:
> I recognize that it is temping to take advantage of the huge address =20=

> space that IPv6 offers but my test engineer instincts tell me it is =20=

> unwise to do so.
>
>
> I too am an engineer, but solid engineering instincts do not tell us =20=

> to use only those facilities whose numbers or sizes can be tested =20
> exhaustively.  If it were so, we would not have multi-terabyte disk =20=

> drives today.
>
> The /64 minimum routable subnet of IPv6 address space was not =20
> designed as it was because people were expected to need 2^64 NIC =20
> cards in their PCs.  This immense per-user address block was created =20=

> because IPv6 designers could see beyond IPv4's use of addresses for =20=

> host interface identification, and were visionary enough to realize =20=

> that all objects could benefit from network addressability.  This =20
> also happens to be one of the key messages of REST.  Addressability =20=

> is extremely important, the finer the better, not only on the Web, =20
> and not only with URIs.
>
> With IPv6 just around the corner, I foresee such addressability at =20
> fine levels of granularity appearing in VWs relatively soon.  IPv4 =20
> worlds will have to emulate what IPv6 worlds achieve natively, and =20
> that is the right way around.  When legacy design restricts =20
> progress, the only thing it achieves is rapid obsolescence.
>
> I would prefer VWRAP not to be painting itself into an IPv4 corner =20
> of obsolescence before it's even released, which is why I'm raising =20=

> this topic --- it's intended as a heads-up for the group.
>
> Since the rise of VWs and IPv6 take-up are going to occur =20
> concurrently, I think the next few years are going to be very =20
> interesting on the VW networking front.  My recommendation is to =20
> observe carefully what happens, and not to make any rash decisions =20
> based on legacy ideas that could cut off your future.
>
>
> Morgaine.
>
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> On Thu, May 20, 2010 at 10:59 AM, Han Sontse =20
> <han.sontse.sl@gmail.com> wrote:
> It's a bad idea to use IP addresses for anything other than =20
> addressing a machine level interface.  Using them to interface =20
> objects at or above the application level is asking for trouble.   =20
> UUIDs are UUIDs... IP addresses are IP addresses.   The two should =20
> not be mixed.   I recognize that it is temping to take advantage of =20=

> the huge address space that IPv6 offers but my test engineer =20
> instincts tell me it is unwise to do so.
>
> Han.
>
> On May 20, 2010, at 2:50 AM, Morgaine wrote:
>
>> A /64 is the smallest routable IPv6 subnet, hence there is no extra =20=

>> routing overhead for the 2^(128-64) addresses in the basic block =20
>> that every user will have allocated.
>>
>> Needless to say, there won't be anything like 2^64 objects in your =20=

>> scenegraph, so if you use your IPv6 address space to address every =20=

>> scenegraph object that you have instantiated client-side, you will =20=

>> still have an extremely sparsely used /64 block.  You'll be keeping =20=

>> track of which addresses you have assigned dynamically of course. =20
>> (An address space of this size is not linearly scannable in =20
>> realistic time.)
>>
>> In principle this is no different to using UUIDs --- your IPv6 =20
>> micro-servers will have unguessable IPv6 addresses within your /64 =20=

>> block, and it'll be up to you to tell other participants in the =20
>> protocol (for example server-side objects) with which of your IPv6 =20=

>> micro-servers they are to communicate.  This is why an ADT that is =20=

>> supportive of IPv6 operation needs to be able to carry such data =20
>> efficiently --- the UUID is no longer the only 128-bit datum of =20
>> interest.
>>
>> Of course your entire /64 block is routed as one, since there are =20
>> no smaller routable subnets in IPv6, and therefore your objections =20=

>> about routing non-scalability do not apply.
>>
>>
>> Morgaine.
>>
>>
>>
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> On Wed, May 19, 2010 at 10:56 PM, Richard Barnes <rbarnes@bbn.com> =20=

>> wrote:
>> The impact of IPv6 on VWs should be far less than you imagine, I =20
>> think. :)
>>
>> It has often been said that many, many things will be assigned IPv6 =20=

>> addresses.  There will certainly be enough to go around, but that =20
>> doesn't make them good application-layer identifiers.  If you want =20=

>> to use IP addresses with IP, they have to route, and that means =20
>> that they have to be either (1) topologically assigned, or (2) =20
>> overlay routed, e.g., with mobile IP.  So if you want to use an IP =20=

>> address to address something, you're going to have to either change =20=

>> that address when the thing gets connected differently, or you'll =20
>> need some overlay routing scheme to route to a persistent address.  =20=

>> (And if you're not going to use the address with IP, then why would =20=

>> you use an IP address?)
>>
>> VWRAP, as an application layer protocol, has a choice about what =20
>> identifiers to use for things and how to use those identifiers.  =20
>> ISTM that using IP addresses (again, of either type) remains a bad =20=

>> idea, compared with something that is decoupled from the routing =20
>> layer.
>>
>> As far as the DNS, I'm not sure what your point is:
>> (i) DNS caching has been around for decades
>> (ii) DNS names can already refer to multiple addresses
>> (iii) Depends on implementation.  Maybe there's some application-=20
>> layer way to resolve names.  E.g., SIP endpoints don't need to have =20=

>> DNS records because the INVITE transaction maps from SIP URIs to IP =20=

>> addresses.
>> (iv) =46rom RFC 4291: "IPv6 addresses are 128-bit identifiers for =20
>> interfaces and sets of
>> interfaces"
>> (v) Seems like there's a use case lurking, hard to address without =20=

>> details.  But you're probably still at the application layer.  For =20=

>> instance, if you were telling your peer to send you an HTTP =20
>> request, you would send an HTTP URI, which can already handle IPv6 =20=

>> addresses.
>>
>> --Richard
>>
>>
>>
>> On May 19, 2010, at 9:35 AM, Morgaine wrote:
>>
>> The impact of IPv6 on VWs is going to be far greater than you =20
>> imagine, I believe.  As things stand, VWRAP is being designed =20
>> around the features and limitations of IPv4 networking.  It will of =20=

>> course be able to ride on top of IPv6 as a transport, but unable to =20=

>> benefit from its improved feature set, unless we provide the means =20=

>> to do so.
>>
>> The question "Why is there ever a need to carry an IP address in =20
>> this application-layer protocol, as opposed to, say, a DNS name or =20=

>> a URI?" suggests an IPv4 mindset, because in IPv6 it has a variety =20=

>> of possible answers:  (i) When the DNS lookup has already been done =20=

>> and does not need to be done again, (ii) When a FQDN maps to =20
>> multiple addresses, but you want to refer to a specific one, (iii) =20=

>> When an IPv6 address does not have an external address record, (iv) =20=

>> When the host is already known and the IP address denotes something =20=

>> other than a physical NIC interface, or (v) When listeners are =20
>> allocated locally and dynamically for the current session only, and =20=

>> their IP addresses need to be communicated to a peer --- this will =20=

>> be an extremely common use case with IPv6.
>>
>> In today's IPv4-based systems, it is normal for a user's machine to =20=

>> have a single IP address, and for a client on that machine to talk =20=

>> to a server that has a single customer-facing IP address too =20
>> (although it may also have others that are not public).  In IPv6-=20
>> based systems, this simple scenario is still possible but =20
>> represents only a special case among a new and vastly expanded set =20=

>> of IPv6 use cases.
>>
>> The smallest allocatable block of IPv6 address space is a /64, so =20
>> 2^(128-64) IP addresses is the number that most normal IPv6 users =20
>> will have, although the much larger /48 blocks of 2^80 addresses =20
>> are commonly assigned to users as well.  With such IP riches client-=20=

>> side, it is certain that they will be used for something, and the =20
>> obvious suggestion is to give every VW object an IPv6 address of =20
>> its own.
>>
>> Lest we forget, one of the most important properties of the REST =20
>> paradigm is addressability, but the benefits of high addressability =20=

>> go far beyond the Web.  This is a property that will become =20
>> ubiquitous throughout networked computing with IPv6.  It's probably =20=

>> no exaggeration to say that *everything* will be getting its own IP =20=

>> address. :-)
>>
>> Faced with that future, it's a mistake to think in IPv4 terms and =20
>> consider IPv6 addresses as merely denoting a host which can be =20
>> obtained from its FQDN.  That's IPv4 thinking, and represents only =20=

>> a very basic use case for IPv6.  In more extended use cases, IPv6 =20
>> addresses will become much more like active local UUIDs than like =20
>> today's host IP addresses.  They will be used for inner-application =20=

>> addressing, for example to make every object in an application an =20
>> addressable micro-server.
>>
>> VWRAP is being born into an IPv6 world, and it would be a mistake =20
>> to hardwire IPv4 thinking into its design.  We continually refer to =20=

>> the need for extensibility and a desire to future-proof the =20
>> protocol, but lip service is not enough.  Adding IPv6 addresses to =20=

>> the underlying ADT would provide a bare minimum level of thinking =20
>> ahead to support VWRAP implementations that embrace large numbers =20
>> of communicating objects.  (A generally extensible ADT would of =20
>> course achieve the same thing, and more.)
>>
>>
>> Morgaine.
>>
>>
>>
>>
>>
>>
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> On Mon, May 17, 2010 at 3:50 PM, David W Levine <dwl@us.ibm.com> =20
>> wrote:
>>
>>
>> vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26 AM:
>>
>> > [image removed]
>> >
>> > Re: [vwrap] VWRAP and IPv6
>> >
>> > Richard Barnes
>> >
>> > to:
>> >
>> > Morgaine
>> >
>> > 05/17/2010 10:09 AM
>> >
>> > Sent by:
>> >
>> > vwrap-bounces@ietf.org
>> >
>> > Cc:
>> >
>> > vwrap
>> >
>> > In the spirit of good layering, it seems like we should be talking
>> > about avoiding direct reliance on IP addresses instead of how we =20=

>> can
>> > accommodate different addresses in the protocol.  Why is there =20
>> ever a
>> > need to carry an IP address in this application-layer protocol, as
>> > opposed to, say, a DNS name or a URI?
>> >
>> > --Richard
>> >
>> +1
>>
>> We may from time to time have a IP address stuck in the form of a URI
>> which has the dotted decimal form of an resource. The spec should =20
>> make
>> sure that form can be an IPV6 address, but that should be very =20
>> straight
>> forward.
>>
>> There may be some IPV6 features which eventually impact us at the =20
>> protocol
>> design level, but the entire VWRAP specification has been written =20
>> in terms of
>> URIs and Capabilities, not in terms of low level IP addresses. It =20
>> would take an
>> incredibly powerful argument to suggest that this should change. =20
>> Likewise, while
>> IPV6 changes addressing at the bottom of the stack, it doesn't =20
>> appreciably change
>> the cost of holding open sessions, of managing sockets and buffers =20=

>> inside of
>> clients (especially lightweight devices) Further while we can all =20
>> devoutly hope
>> that IPV6 finally deploys broadly, making it a dependancy in the =20
>> near term feels
>> rather like a roadblock to possible adoption.
>>
>> - David
>> ~ Zha
>>
>>
>>
>> >
>> > On May 14, 2010, at 7:32 AM, Morgaine wrote:
>> >
>> > > Despite exceedingly low takeup of IPv6 so far, it's coming, and =20=

>> in
>> > > the context of IETF WG rates of progress, it is really =20
>> imminent.  Of
>> > > special relevance to us is that IPv4 addresses are projected to =20=

>> run
>> > > out within roughly the same time frame as VWRAP materializes.
>> > >
>> > > There is little point in creating a new VW protocol today =20
>> purely in
>> > > the context of IPv4 without thinking about tomorrow's IPv6
>> > > environment.  By the time that VWRAP is fully defined, we should
>> > > expect a substantial and rapidly increasing proportion of VWRAP
>> > > implementations to occur in IPv6-accessible worlds.  This is a
>> > > situation for which we need to plan now, otherwise the protocol =20=

>> will
>> > > be obsolete before it's even ready.
>> > >
>> > > To get the ball rolling, here are a few IPv6-related issues =20
>> that we
>> > > could usefully address in the group:
>> > >
>> > >    =95 The 128-bit IP address of IPv6 is likely to become a =
common
>> > > payload, so it should be supported natively.  LLSD already =20
>> supports
>> > > one 128-bit data type of course, the UUID.  IPv6 addresses should
>> > > not be transported in UUID fields however, since their =20
>> statistical
>> > > properties and semantics are totally different.  In any case, the
>> > > two spaces are disjoint so confusing them would be a mistake.  =20=

>> The
>> > > IPv6 address seems a good candidate for its own defined type, =20
>> in the
>> > > absence of wide integers.
>> > >    =95 The extremely large address space of IPv6 has often been
>> > > portrayed as allowing everything around us to have its own IP
>> > > address.  In the context of virtual worlds, this idea can =20
>> actually
>> > > be put to good use, with each virtual object bearing its own IPv6
>> > > address.  One candidate application for this has already been
>> > > described in earlier discussions --- for example, implementing
>> > > virtual object simulation in two parts, one client-side and one
>> > > world-side, the two parts communicating directly.  IPv6 =20
>> addressing
>> > > of objects makes this relatively easy to achieve efficiently, =20
>> so its
>> > > implementation in IPv6-based worlds is almost inevitable before
>> > > long.  VWRAP should be ready for this.
>> > >    =95 The event queue in current implementations provides an =20
>> indirect
>> > > and highly inefficient way of achieving world-to-client
>> > > communications.  IPv6 offers opportunities for direct =20
>> communication
>> > > that can make the event queue approach obsolete, so it's worth
>> > > examining IPv6-oriented alternatives.
>> > >    =95 We recently discussed feature and protocol negotiation =20
>> within
>> > > VWRAP.  IPv6 provides much opportunity for new features and =20
>> protocol
>> > > pathways to be negotiated between endpoints, so it gives us a =20
>> very
>> > > real and imminent set of use cases for negotiation.
>> > >
>> > > It would also be a feather in VWRAP's cap to be considered an =20
>> "IPv6-
>> > > capable application protocol" in a stronger sense than just to be
>> > > carried by IPv6 networks.  IPv6 does after all bring new =20
>> abilities
>> > > to the table, such as the huge addressing, and it would be a =20
>> mistake
>> > > to ignore them.
>> > >
>> > >
>> > > Morgaine.
>> > >
>> > >
>> > >
>> > > _______________________________________________
>> > > vwrap mailing list
>> > > vwrap@ietf.org
>> > > https://www.ietf.org/mailman/listinfo/vwrap
>> >
>> > _______________________________________________
>> > vwrap mailing list
>> > vwrap@ietf.org
>> > https://www.ietf.org/mailman/listinfo/vwrap
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap


From morgaine.dinova@googlemail.com  Thu May 20 07:47:01 2010
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 368EB3A6936 for <vwrap@core3.amsl.com>; Thu, 20 May 2010 07:47:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.802
X-Spam-Level: 
X-Spam-Status: No, score=0.802 tagged_above=-999 required=5 tests=[AWL=0.179,  BAYES_50=0.001, 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 Jndit6axkS8Z for <vwrap@core3.amsl.com>; Thu, 20 May 2010 07:46:58 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 0E8763A6994 for <vwrap@ietf.org>; Thu, 20 May 2010 07:46:56 -0700 (PDT)
Received: by wyb32 with SMTP id 32so1637982wyb.31 for <vwrap@ietf.org>; Thu, 20 May 2010 07:46:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=eddvLk+r8DPz9EIPkxtGN/ikpGzaS6JhvRQbLK4TKSk=; b=vBJxZ/N89Ma2WE53adWlySpDdayOl39Ty5OMR0ZqC8OVxbIHuEThuJOY6L4G0PK1D4 Jd63igNhvqEGkwkyZPr41L4bM+hjLXasYqekTUV9bugMZUMZhUibHzzj4eUdDGFi6TCo k6da4VniRRDBaxIAHtSvU4uE1xJp+F0WKkDNE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=gneMjxCq6rhulGYa7FdmyhIf16IM6/B2F2jLbBokGXbvNwHU9H/ZCiif6VAenMV46/ OS9XkjGQi/l7i1HGzJmnTV6TKk3hUVhrHjpbGied93uqgfCYVvc3d5NqJPBbPibEDcoO qcAGcf1Slmh8k71aWKbL4mQp+pXLmoefL5R/E=
MIME-Version: 1.0
Received: by 10.216.161.14 with SMTP id v14mr1976131wek.179.1274366806859;  Thu, 20 May 2010 07:46:46 -0700 (PDT)
Received: by 10.216.26.132 with HTTP; Thu, 20 May 2010 07:46:46 -0700 (PDT)
In-Reply-To: <B2E410EF-1AD1-45E6-88A3-BE18FCC1571F@bbn.com>
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com> <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com> <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com> <632C4898-F7DD-4B76-AAFB-D675346E2521@gmail.com> <AANLkTik42H1xhnr_yljo06-4thbaT3GcLBDabzoj2c2t@mail.gmail.com> <B2E410EF-1AD1-45E6-88A3-BE18FCC1571F@bbn.com>
Date: Thu, 20 May 2010 15:46:46 +0100
Message-ID: <AANLkTikqBQPp-o_u58tas669x55n7bZ1R3oXSoaG2q3Z@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary=0016367fb68bd6204e048707a4aa
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 14:47:01 -0000

--0016367fb68bd6204e048707a4aa
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Abstracting over addresses is fine, Richard, but after you've dealt with th=
e
abstractions you typically end up with addresses, and that's what protocols
work with from then on.

The textual abstractions are only there for human comfort, ease of
configuration, and great flexibility of indirection, but abstractions are
just means to an end.  After the address abstractions are de-abstracted,
protocols work with the much more efficient binary representations.  That's
practically universal.

It's easy to give a practical example of such operation.  For example,
consider a design in which all VW objects have two parts, an in-world objec=
t
(IWO) and an in-client object (ICO), where the ICO is replicated in each
client.  Let both parts be active, ie. both sides can be event generators.
It's easy for ICOs to address update events to their IWO because there is
only one IWO, and access could be optimized to network level after the
de-abstraction step for efficiency.  But what about updates in the reverse
direction, which is 1:N?

In the typical IPv4 environment, the usual approach would be a heavily
indirected one, with updates travelling through layer upon layer of
middleware before reaching their target ICO.  In an IPv6 environment in
which each ICO can have its own IPv6 address, there need be no middleware a=
t
all between the host kernel and the target object.  The resulting increase
in efficiency by orders of magnitude can have major ramifications on the
operation of your world and of your clients.

And the cost of this massive leap in efficiency?  Merely to inform the IWO
of the ICO's dynamic IPv6 network address, which borders on the trivial.

One of my main interests is VW scalability, both of worlds and of clients,
and such efficiency gains are truly important.  Scaling VW complexity and
rendering of crowds or of highly detailed visualizations requires some
lateral thinking and more powerful networking paradigms than we have been
used to until now.  IPv6 offers some interesting solutions in that
direction, and they will be used.


Morgaine.





=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

On Thu, May 20, 2010 at 2:43 PM, Richard Barnes <rbarnes@bbn.com> wrote:

> As an aside, there's nothing that says that subscribers have to be
> allocated a /64.  Some proposed addressing schemes that are more
> conservative (in the Asia/Pacific region IIRC) actually assign much longe=
r
> prefixes (smaller address blocks) to customers.
>
> Fine-grained addressability is not the same as fine-grained allocation of
> *IP* addresses. Think of it this way: HTTP has very fine-grained
> addressability, with individual identifier/locators for pages, images,
> scripts, etc.  It's able to accomplish this not by assigning an IPv6 addr=
ess
> to every object, but by using an application-layer identifier/locator --
> namely a URL.
>
> Not using IPv6 addresses in applications is not painting oneself into an
> IPv4 corner, it's good protocol design following the layering model of th=
e
> Internet.  (If we're using IPv4 addresses for identifiers, we shouldn't b=
e
> doing that either!)  Abstracting over IP addresses is about freeing the
> application from having to worry about whether its IPv4 or IPv6 or IPv10 =
or
> X.25 or whatever else at the network layer.
>
> --Richard
>
>
>
>
> On May 20, 2010, at 9:23 AM, Morgaine wrote:
>
>  On Thu, May 20, 2010 at 10:59 AM, Han Sontse <han.sontse.sl@gmail.com>
>> wrote:
>> I recognize that it is temping to take advantage of the huge address spa=
ce
>> that IPv6 offers but my test engineer instincts tell me it is unwise to =
do
>> so.
>>
>>
>> I too am an engineer, but solid engineering instincts do not tell us to
>> use only those facilities whose numbers or sizes can be tested exhaustiv=
ely.
>>  If it were so, we would not have multi-terabyte disk drives today.
>>
>> The /64 minimum routable subnet of IPv6 address space was not designed a=
s
>> it was because people were expected to need 2^64 NIC cards in their PCs.
>>  This immense per-user address block was created because IPv6 designers
>> could see beyond IPv4's use of addresses for host interface identificati=
on,
>> and were visionary enough to realize that all objects could benefit from
>> network addressability.  This also happens to be one of the key messages=
 of
>> REST.  Addressability is extremely important, the finer the better, not =
only
>> on the Web, and not only with URIs.
>>
>> With IPv6 just around the corner, I foresee such addressability at fine
>> levels of granularity appearing in VWs relatively soon.  IPv4 worlds wil=
l
>> have to emulate what IPv6 worlds achieve natively, and that is the right=
 way
>> around.  When legacy design restricts progress, the only thing it achiev=
es
>> is rapid obsolescence.
>>
>> I would prefer VWRAP not to be painting itself into an IPv4 corner of
>> obsolescence before it's even released, which is why I'm raising this to=
pic
>> --- it's intended as a heads-up for the group.
>>
>> Since the rise of VWs and IPv6 take-up are going to occur concurrently, =
I
>> think the next few years are going to be very interesting on the VW
>> networking front.  My recommendation is to observe carefully what happen=
s,
>> and not to make any rash decisions based on legacy ideas that could cut =
off
>> your future.
>>
>>
>> Morgaine.
>>
>>
>>
>>
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> On Thu, May 20, 2010 at 10:59 AM, Han Sontse <han.sontse.sl@gmail.com>
>> wrote:
>> It's a bad idea to use IP addresses for anything other than addressing a
>> machine level interface.  Using them to interface objects at or above th=
e
>> application level is asking for trouble.   UUIDs are UUIDs... IP address=
es
>> are IP addresses.   The two should not be mixed.   I recognize that it i=
s
>> temping to take advantage of the huge address space that IPv6 offers but=
 my
>> test engineer instincts tell me it is unwise to do so.
>>
>> Han.
>>
>> On May 20, 2010, at 2:50 AM, Morgaine wrote:
>>
>>  A /64 is the smallest routable IPv6 subnet, hence there is no extra
>>> routing overhead for the 2^(128-64) addresses in the basic block that e=
very
>>> user will have allocated.
>>>
>>> Needless to say, there won't be anything like 2^64 objects in your
>>> scenegraph, so if you use your IPv6 address space to address every
>>> scenegraph object that you have instantiated client-side, you will stil=
l
>>> have an extremely sparsely used /64 block.  You'll be keeping track of =
which
>>> addresses you have assigned dynamically of course. (An address space of=
 this
>>> size is not linearly scannable in realistic time.)
>>>
>>> In principle this is no different to using UUIDs --- your IPv6
>>> micro-servers will have unguessable IPv6 addresses within your /64 bloc=
k,
>>> and it'll be up to you to tell other participants in the protocol (for
>>> example server-side objects) with which of your IPv6 micro-servers they=
 are
>>> to communicate.  This is why an ADT that is supportive of IPv6 operatio=
n
>>> needs to be able to carry such data efficiently --- the UUID is no long=
er
>>> the only 128-bit datum of interest.
>>>
>>> Of course your entire /64 block is routed as one, since there are no
>>> smaller routable subnets in IPv6, and therefore your objections about
>>> routing non-scalability do not apply.
>>>
>>>
>>> Morgaine.
>>>
>>>
>>>
>>>
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>
>>> On Wed, May 19, 2010 at 10:56 PM, Richard Barnes <rbarnes@bbn.com>
>>> wrote:
>>> The impact of IPv6 on VWs should be far less than you imagine, I think.
>>> :)
>>>
>>> It has often been said that many, many things will be assigned IPv6
>>> addresses.  There will certainly be enough to go around, but that doesn=
't
>>> make them good application-layer identifiers.  If you want to use IP
>>> addresses with IP, they have to route, and that means that they have to=
 be
>>> either (1) topologically assigned, or (2) overlay routed, e.g., with mo=
bile
>>> IP.  So if you want to use an IP address to address something, you're g=
oing
>>> to have to either change that address when the thing gets connected
>>> differently, or you'll need some overlay routing scheme to route to a
>>> persistent address.  (And if you're not going to use the address with I=
P,
>>> then why would you use an IP address?)
>>>
>>> VWRAP, as an application layer protocol, has a choice about what
>>> identifiers to use for things and how to use those identifiers.  ISTM t=
hat
>>> using IP addresses (again, of either type) remains a bad idea, compared=
 with
>>> something that is decoupled from the routing layer.
>>>
>>> As far as the DNS, I'm not sure what your point is:
>>> (i) DNS caching has been around for decades
>>> (ii) DNS names can already refer to multiple addresses
>>> (iii) Depends on implementation.  Maybe there's some application-layer
>>> way to resolve names.  E.g., SIP endpoints don't need to have DNS recor=
ds
>>> because the INVITE transaction maps from SIP URIs to IP addresses.
>>> (iv) From RFC 4291: "IPv6 addresses are 128-bit identifiers for
>>> interfaces and sets of
>>> interfaces"
>>> (v) Seems like there's a use case lurking, hard to address without
>>> details.  But you're probably still at the application layer.  For inst=
ance,
>>> if you were telling your peer to send you an HTTP request, you would se=
nd an
>>> HTTP URI, which can already handle IPv6 addresses.
>>>
>>> --Richard
>>>
>>>
>>>
>>> On May 19, 2010, at 9:35 AM, Morgaine wrote:
>>>
>>> The impact of IPv6 on VWs is going to be far greater than you imagine, =
I
>>> believe.  As things stand, VWRAP is being designed around the features =
and
>>> limitations of IPv4 networking.  It will of course be able to ride on t=
op of
>>> IPv6 as a transport, but unable to benefit from its improved feature se=
t,
>>> unless we provide the means to do so.
>>>
>>> The question "Why is there ever a need to carry an IP address in this
>>> application-layer protocol, as opposed to, say, a DNS name or a URI?"
>>> suggests an IPv4 mindset, because in IPv6 it has a variety of possible
>>> answers:  (i) When the DNS lookup has already been done and does not ne=
ed to
>>> be done again, (ii) When a FQDN maps to multiple addresses, but you wan=
t to
>>> refer to a specific one, (iii) When an IPv6 address does not have an
>>> external address record, (iv) When the host is already known and the IP
>>> address denotes something other than a physical NIC interface, or (v) W=
hen
>>> listeners are allocated locally and dynamically for the current session
>>> only, and their IP addresses need to be communicated to a peer --- this=
 will
>>> be an extremely common use case with IPv6.
>>>
>>> In today's IPv4-based systems, it is normal for a user's machine to hav=
e
>>> a single IP address, and for a client on that machine to talk to a serv=
er
>>> that has a single customer-facing IP address too (although it may also =
have
>>> others that are not public).  In IPv6-based systems, this simple scenar=
io is
>>> still possible but represents only a special case among a new and vastl=
y
>>> expanded set of IPv6 use cases.
>>>
>>> The smallest allocatable block of IPv6 address space is a /64, so
>>> 2^(128-64) IP addresses is the number that most normal IPv6 users will =
have,
>>> although the much larger /48 blocks of 2^80 addresses are commonly assi=
gned
>>> to users as well.  With such IP riches client-side, it is certain that =
they
>>> will be used for something, and the obvious suggestion is to give every=
 VW
>>> object an IPv6 address of its own.
>>>
>>> Lest we forget, one of the most important properties of the REST paradi=
gm
>>> is addressability, but the benefits of high addressability go far beyon=
d the
>>> Web.  This is a property that will become ubiquitous throughout network=
ed
>>> computing with IPv6.  It's probably no exaggeration to say that *everyt=
hing*
>>> will be getting its own IP address. :-)
>>>
>>> Faced with that future, it's a mistake to think in IPv4 terms and
>>> consider IPv6 addresses as merely denoting a host which can be obtained=
 from
>>> its FQDN.  That's IPv4 thinking, and represents only a very basic use c=
ase
>>> for IPv6.  In more extended use cases, IPv6 addresses will become much =
more
>>> like active local UUIDs than like today's host IP addresses.  They will=
 be
>>> used for inner-application addressing, for example to make every object=
 in
>>> an application an addressable micro-server.
>>>
>>> VWRAP is being born into an IPv6 world, and it would be a mistake to
>>> hardwire IPv4 thinking into its design.  We continually refer to the ne=
ed
>>> for extensibility and a desire to future-proof the protocol, but lip se=
rvice
>>> is not enough.  Adding IPv6 addresses to the underlying ADT would provi=
de a
>>> bare minimum level of thinking ahead to support VWRAP implementations t=
hat
>>> embrace large numbers of communicating objects.  (A generally extensibl=
e ADT
>>> would of course achieve the same thing, and more.)
>>>
>>>
>>> Morgaine.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>
>>> On Mon, May 17, 2010 at 3:50 PM, David W Levine <dwl@us.ibm.com> wrote:
>>>
>>>
>>> vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26 AM:
>>>
>>> > [image removed]
>>> >
>>> > Re: [vwrap] VWRAP and IPv6
>>> >
>>> > Richard Barnes
>>> >
>>> > to:
>>> >
>>> > Morgaine
>>> >
>>> > 05/17/2010 10:09 AM
>>> >
>>> > Sent by:
>>> >
>>> > vwrap-bounces@ietf.org
>>> >
>>> > Cc:
>>> >
>>> > vwrap
>>> >
>>> > In the spirit of good layering, it seems like we should be talking
>>> > about avoiding direct reliance on IP addresses instead of how we can
>>> > accommodate different addresses in the protocol.  Why is there ever a
>>> > need to carry an IP address in this application-layer protocol, as
>>> > opposed to, say, a DNS name or a URI?
>>> >
>>> > --Richard
>>> >
>>> +1
>>>
>>> We may from time to time have a IP address stuck in the form of a URI
>>> which has the dotted decimal form of an resource. The spec should make
>>> sure that form can be an IPV6 address, but that should be very straight
>>> forward.
>>>
>>> There may be some IPV6 features which eventually impact us at the
>>> protocol
>>> design level, but the entire VWRAP specification has been written in
>>> terms of
>>> URIs and Capabilities, not in terms of low level IP addresses. It would
>>> take an
>>> incredibly powerful argument to suggest that this should change.
>>> Likewise, while
>>> IPV6 changes addressing at the bottom of the stack, it doesn't
>>> appreciably change
>>> the cost of holding open sessions, of managing sockets and buffers insi=
de
>>> of
>>> clients (especially lightweight devices) Further while we can all
>>> devoutly hope
>>> that IPV6 finally deploys broadly, making it a dependancy in the near
>>> term feels
>>> rather like a roadblock to possible adoption.
>>>
>>> - David
>>> ~ Zha
>>>
>>>
>>>
>>> >
>>> > On May 14, 2010, at 7:32 AM, Morgaine wrote:
>>> >
>>> > > Despite exceedingly low takeup of IPv6 so far, it's coming, and in
>>> > > the context of IETF WG rates of progress, it is really imminent.  O=
f
>>> > > special relevance to us is that IPv4 addresses are projected to run
>>> > > out within roughly the same time frame as VWRAP materializes.
>>> > >
>>> > > There is little point in creating a new VW protocol today purely in
>>> > > the context of IPv4 without thinking about tomorrow's IPv6
>>> > > environment.  By the time that VWRAP is fully defined, we should
>>> > > expect a substantial and rapidly increasing proportion of VWRAP
>>> > > implementations to occur in IPv6-accessible worlds.  This is a
>>> > > situation for which we need to plan now, otherwise the protocol wil=
l
>>> > > be obsolete before it's even ready.
>>> > >
>>> > > To get the ball rolling, here are a few IPv6-related issues that we
>>> > > could usefully address in the group:
>>> > >
>>> > >    =95 The 128-bit IP address of IPv6 is likely to become a common
>>> > > payload, so it should be supported natively.  LLSD already supports
>>> > > one 128-bit data type of course, the UUID.  IPv6 addresses should
>>> > > not be transported in UUID fields however, since their statistical
>>> > > properties and semantics are totally different.  In any case, the
>>> > > two spaces are disjoint so confusing them would be a mistake.  The
>>> > > IPv6 address seems a good candidate for its own defined type, in th=
e
>>> > > absence of wide integers.
>>> > >    =95 The extremely large address space of IPv6 has often been
>>> > > portrayed as allowing everything around us to have its own IP
>>> > > address.  In the context of virtual worlds, this idea can actually
>>> > > be put to good use, with each virtual object bearing its own IPv6
>>> > > address.  One candidate application for this has already been
>>> > > described in earlier discussions --- for example, implementing
>>> > > virtual object simulation in two parts, one client-side and one
>>> > > world-side, the two parts communicating directly.  IPv6 addressing
>>> > > of objects makes this relatively easy to achieve efficiently, so it=
s
>>> > > implementation in IPv6-based worlds is almost inevitable before
>>> > > long.  VWRAP should be ready for this.
>>> > >    =95 The event queue in current implementations provides an indir=
ect
>>> > > and highly inefficient way of achieving world-to-client
>>> > > communications.  IPv6 offers opportunities for direct communication
>>> > > that can make the event queue approach obsolete, so it's worth
>>> > > examining IPv6-oriented alternatives.
>>> > >    =95 We recently discussed feature and protocol negotiation withi=
n
>>> > > VWRAP.  IPv6 provides much opportunity for new features and protoco=
l
>>> > > pathways to be negotiated between endpoints, so it gives us a very
>>> > > real and imminent set of use cases for negotiation.
>>> > >
>>> > > It would also be a feather in VWRAP's cap to be considered an "IPv6=
-
>>> > > capable application protocol" in a stronger sense than just to be
>>> > > carried by IPv6 networks.  IPv6 does after all bring new abilities
>>> > > to the table, such as the huge addressing, and it would be a mistak=
e
>>> > > to ignore them.
>>> > >
>>> > >
>>> > > Morgaine.
>>> > >
>>> > >
>>> > >
>>> > > _______________________________________________
>>> > > vwrap mailing list
>>> > > vwrap@ietf.org
>>> > > https://www.ietf.org/mailman/listinfo/vwrap
>>> >
>>> > _______________________________________________
>>> > vwrap mailing list
>>> > vwrap@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/vwrap
>>>
>>> _______________________________________________
>>> vwrap mailing list
>>> vwrap@ietf.org
>>> https://www.ietf.org/mailman/listinfo/vwrap
>>>
>>> _______________________________________________
>>> vwrap mailing list
>>> vwrap@ietf.org
>>> https://www.ietf.org/mailman/listinfo/vwrap
>>>
>>> _______________________________________________
>>> vwrap mailing list
>>> vwrap@ietf.org
>>> https://www.ietf.org/mailman/listinfo/vwrap
>>>
>>
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>
>

--0016367fb68bd6204e048707a4aa
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Abstracting over addresses is fine, Richard, but after you&#39;ve dealt wit=
h the abstractions you typically end up with addresses, and that&#39;s what=
 protocols work with from then on.<br><br>The textual abstractions are only=
 there for human comfort, ease of configuration, and great flexibility of i=
ndirection, but abstractions are just means to an end.=A0 After the address=
 abstractions are de-abstracted, protocols work with the much more efficien=
t binary representations.=A0 That&#39;s practically universal.<br>
<br>It&#39;s easy to give a practical example of such operation.=A0 For exa=
mple, consider a design in which all VW objects have two parts, an in-world=
 object (IWO) and an in-client object (ICO), where the ICO is replicated in=
 each client.=A0 Let both parts be active, ie. both sides can be event gene=
rators.=A0 It&#39;s easy for ICOs to address update events to their IWO bec=
ause there is only one IWO, and access could be optimized to network level =
after the de-abstraction step for efficiency.=A0 But what about updates in =
the reverse direction, which is 1:N?<br>
<br>In the typical IPv4 environment, the usual approach would be a heavily =
indirected one, with updates travelling through layer upon layer of middlew=
are before reaching their target ICO.=A0 In an IPv6 environment in which ea=
ch ICO can have its own IPv6 address, there need be no middleware at all be=
tween the host kernel and the target object.=A0 The resulting increase in e=
fficiency by orders of magnitude can have major ramifications on the operat=
ion of your world and of your clients.<br>
<br>And the cost of this massive leap in efficiency?=A0 Merely to inform th=
e IWO of the ICO&#39;s dynamic IPv6 network address, which borders on the t=
rivial.<br><br>One of my main interests is VW scalability, both of worlds a=
nd of clients, and such efficiency gains are truly important.=A0 Scaling VW=
 complexity and rendering of crowds or of highly detailed visualizations re=
quires some lateral thinking and more powerful networking paradigms than we=
 have been used to until now.=A0 IPv6 offers some interesting solutions in =
that direction, and they will be used.<br>
<br><br>Morgaine.<br><br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><b=
r><div class=3D"gmail_quote">On Thu, May 20, 2010 at 2:43 PM, Richard Barne=
s <span dir=3D"ltr">&lt;<a href=3D"mailto:rbarnes@bbn.com">rbarnes@bbn.com<=
/a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">As an aside, ther=
e&#39;s nothing that says that subscribers have to be allocated a /64. =A0S=
ome proposed addressing schemes that are more conservative (in the Asia/Pac=
ific region IIRC) actually assign much longer prefixes (smaller address blo=
cks) to customers.<br>

<br>
Fine-grained addressability is not the same as fine-grained allocation of *=
IP* addresses. Think of it this way: HTTP has very fine-grained addressabil=
ity, with individual identifier/locators for pages, images, scripts, etc. =
=A0It&#39;s able to accomplish this not by assigning an IPv6 address to eve=
ry object, but by using an application-layer identifier/locator -- namely a=
 URL.<br>

<br>
Not using IPv6 addresses in applications is not painting oneself into an IP=
v4 corner, it&#39;s good protocol design following the layering model of th=
e Internet. =A0(If we&#39;re using IPv4 addresses for identifiers, we shoul=
dn&#39;t be doing that either!) =A0Abstracting over IP addresses is about f=
reeing the application from having to worry about whether its IPv4 or IPv6 =
or IPv10 or X.25 or whatever else at the network layer.<br>
<font color=3D"#888888">
<br>
--Richard</font><div><div></div><div class=3D"h5"><br>
<br>
<br>
<br>
On May 20, 2010, at 9:23 AM, Morgaine wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, May 20, 2010 at 10:59 AM, Han Sontse &lt;<a href=3D"http://han.sont=
se.sl" target=3D"_blank">han.sontse.sl</a>@<a href=3D"http://gmail.com" tar=
get=3D"_blank">gmail.com</a>&gt; wrote:<br>
I recognize that it is temping to take advantage of the huge address space =
that IPv6 offers but my test engineer instincts tell me it is unwise to do =
so.<br>
<br>
<br>
I too am an engineer, but solid engineering instincts do not tell us to use=
 only those facilities whose numbers or sizes can be tested exhaustively. =
=A0If it were so, we would not have multi-terabyte disk drives today.<br>

<br>
The /64 minimum routable subnet of IPv6 address space was not designed as i=
t was because people were expected to need 2^64 NIC cards in their PCs. =A0=
This immense per-user address block was created because IPv6 designers coul=
d see beyond IPv4&#39;s use of addresses for host interface identification,=
 and were visionary enough to realize that all objects could benefit from n=
etwork addressability. =A0This also happens to be one of the key messages o=
f REST. =A0Addressability is extremely important, the finer the better, not=
 only on the Web, and not only with URIs.<br>

<br>
With IPv6 just around the corner, I foresee such addressability at fine lev=
els of granularity appearing in VWs relatively soon. =A0IPv4 worlds will ha=
ve to emulate what IPv6 worlds achieve natively, and that is the right way =
around. =A0When legacy design restricts progress, the only thing it achieve=
s is rapid obsolescence.<br>

<br>
I would prefer VWRAP not to be painting itself into an IPv4 corner of obsol=
escence before it&#39;s even released, which is why I&#39;m raising this to=
pic --- it&#39;s intended as a heads-up for the group.<br>
<br>
Since the rise of VWs and IPv6 take-up are going to occur concurrently, I t=
hink the next few years are going to be very interesting on the VW networki=
ng front. =A0My recommendation is to observe carefully what happens, and no=
t to make any rash decisions based on legacy ideas that could cut off your =
future.<br>

<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
On Thu, May 20, 2010 at 10:59 AM, Han Sontse &lt;<a href=3D"http://han.sont=
se.sl" target=3D"_blank">han.sontse.sl</a>@<a href=3D"http://gmail.com" tar=
get=3D"_blank">gmail.com</a>&gt; wrote:<br>
It&#39;s a bad idea to use IP addresses for anything other than addressing =
a machine level interface. =A0Using them to interface objects at or above t=
he application level is asking for trouble. =A0 UUIDs are UUIDs... IP addre=
sses are IP addresses. =A0 The two should not be mixed. =A0 I recognize tha=
t it is temping to take advantage of the huge address space that IPv6 offer=
s but my test engineer instincts tell me it is unwise to do so.<br>

<br>
Han.<br>
<br>
On May 20, 2010, at 2:50 AM, Morgaine wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A /64 is the smallest routable IPv6 subnet, hence there is no extra routing=
 overhead for the 2^(128-64) addresses in the basic block that every user w=
ill have allocated.<br>
<br>
Needless to say, there won&#39;t be anything like 2^64 objects in your scen=
egraph, so if you use your IPv6 address space to address every scenegraph o=
bject that you have instantiated client-side, you will still have an extrem=
ely sparsely used /64 block. =A0You&#39;ll be keeping track of which addres=
ses you have assigned dynamically of course. (An address space of this size=
 is not linearly scannable in realistic time.)<br>

<br>
In principle this is no different to using UUIDs --- your IPv6 micro-server=
s will have unguessable IPv6 addresses within your /64 block, and it&#39;ll=
 be up to you to tell other participants in the protocol (for example serve=
r-side objects) with which of your IPv6 micro-servers they are to communica=
te. =A0This is why an ADT that is supportive of IPv6 operation needs to be =
able to carry such data efficiently --- the UUID is no longer the only 128-=
bit datum of interest.<br>

<br>
Of course your entire /64 block is routed as one, since there are no smalle=
r routable subnets in IPv6, and therefore your objections about routing non=
-scalability do not apply.<br>
<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
On Wed, May 19, 2010 at 10:56 PM, Richard Barnes &lt;<a href=3D"mailto:rbar=
nes@bbn.com" target=3D"_blank">rbarnes@bbn.com</a>&gt; wrote:<br>
The impact of IPv6 on VWs should be far less than you imagine, I think. :)<=
br>
<br>
It has often been said that many, many things will be assigned IPv6 address=
es. =A0There will certainly be enough to go around, but that doesn&#39;t ma=
ke them good application-layer identifiers. =A0If you want to use IP addres=
ses with IP, they have to route, and that means that they have to be either=
 (1) topologically assigned, or (2) overlay routed, e.g., with mobile IP. =
=A0So if you want to use an IP address to address something, you&#39;re goi=
ng to have to either change that address when the thing gets connected diff=
erently, or you&#39;ll need some overlay routing scheme to route to a persi=
stent address. =A0(And if you&#39;re not going to use the address with IP, =
then why would you use an IP address?)<br>

<br>
VWRAP, as an application layer protocol, has a choice about what identifier=
s to use for things and how to use those identifiers. =A0ISTM that using IP=
 addresses (again, of either type) remains a bad idea, compared with someth=
ing that is decoupled from the routing layer.<br>

<br>
As far as the DNS, I&#39;m not sure what your point is:<br>
(i) DNS caching has been around for decades<br>
(ii) DNS names can already refer to multiple addresses<br>
(iii) Depends on implementation. =A0Maybe there&#39;s some application-laye=
r way to resolve names. =A0E.g., SIP endpoints don&#39;t need to have DNS r=
ecords because the INVITE transaction maps from SIP URIs to IP addresses.<b=
r>

(iv) From RFC 4291: &quot;IPv6 addresses are 128-bit identifiers for interf=
aces and sets of<br>
interfaces&quot;<br>
(v) Seems like there&#39;s a use case lurking, hard to address without deta=
ils. =A0But you&#39;re probably still at the application layer. =A0For inst=
ance, if you were telling your peer to send you an HTTP request, you would =
send an HTTP URI, which can already handle IPv6 addresses.<br>

<br>
--Richard<br>
<br>
<br>
<br>
On May 19, 2010, at 9:35 AM, Morgaine wrote:<br>
<br>
The impact of IPv6 on VWs is going to be far greater than you imagine, I be=
lieve. =A0As things stand, VWRAP is being designed around the features and =
limitations of IPv4 networking. =A0It will of course be able to ride on top=
 of IPv6 as a transport, but unable to benefit from its improved feature se=
t, unless we provide the means to do so.<br>

<br>
The question &quot;Why is there ever a need to carry an IP address in this =
application-layer protocol, as opposed to, say, a DNS name or a URI?&quot; =
suggests an IPv4 mindset, because in IPv6 it has a variety of possible answ=
ers: =A0(i) When the DNS lookup has already been done and does not need to =
be done again, (ii) When a FQDN maps to multiple addresses, but you want to=
 refer to a specific one, (iii) When an IPv6 address does not have an exter=
nal address record, (iv) When the host is already known and the IP address =
denotes something other than a physical NIC interface, or (v) When listener=
s are allocated locally and dynamically for the current session only, and t=
heir IP addresses need to be communicated to a peer --- this will be an ext=
remely common use case with IPv6.<br>

<br>
In today&#39;s IPv4-based systems, it is normal for a user&#39;s machine to=
 have a single IP address, and for a client on that machine to talk to a se=
rver that has a single customer-facing IP address too (although it may also=
 have others that are not public). =A0In IPv6-based systems, this simple sc=
enario is still possible but represents only a special case among a new and=
 vastly expanded set of IPv6 use cases.<br>

<br>
The smallest allocatable block of IPv6 address space is a /64, so 2^(128-64=
) IP addresses is the number that most normal IPv6 users will have, althoug=
h the much larger /48 blocks of 2^80 addresses are commonly assigned to use=
rs as well. =A0With such IP riches client-side, it is certain that they wil=
l be used for something, and the obvious suggestion is to give every VW obj=
ect an IPv6 address of its own.<br>

<br>
Lest we forget, one of the most important properties of the REST paradigm i=
s addressability, but the benefits of high addressability go far beyond the=
 Web. =A0This is a property that will become ubiquitous throughout networke=
d computing with IPv6. =A0It&#39;s probably no exaggeration to say that *ev=
erything* will be getting its own IP address. :-)<br>

<br>
Faced with that future, it&#39;s a mistake to think in IPv4 terms and consi=
der IPv6 addresses as merely denoting a host which can be obtained from its=
 FQDN. =A0That&#39;s IPv4 thinking, and represents only a very basic use ca=
se for IPv6. =A0In more extended use cases, IPv6 addresses will become much=
 more like active local UUIDs than like today&#39;s host IP addresses. =A0T=
hey will be used for inner-application addressing, for example to make ever=
y object in an application an addressable micro-server.<br>

<br>
VWRAP is being born into an IPv6 world, and it would be a mistake to hardwi=
re IPv4 thinking into its design. =A0We continually refer to the need for e=
xtensibility and a desire to future-proof the protocol, but lip service is =
not enough. =A0Adding IPv6 addresses to the underlying ADT would provide a =
bare minimum level of thinking ahead to support VWRAP implementations that =
embrace large numbers of communicating objects. =A0(A generally extensible =
ADT would of course achieve the same thing, and more.)<br>

<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
On Mon, May 17, 2010 at 3:50 PM, David W Levine &lt;<a href=3D"mailto:dwl@u=
s.ibm.com" target=3D"_blank">dwl@us.ibm.com</a>&gt; wrote:<br>
<br>
<br>
<a href=3D"mailto:vwrap-bounces@ietf.org" target=3D"_blank">vwrap-bounces@i=
etf.org</a> wrote on 05/17/2010 10:08:26 AM:<br>
<br>
&gt; [image removed]<br>
&gt;<br>
&gt; Re: [vwrap] VWRAP and IPv6<br>
&gt;<br>
&gt; Richard Barnes<br>
&gt;<br>
&gt; to:<br>
&gt;<br>
&gt; Morgaine<br>
&gt;<br>
&gt; 05/17/2010 10:09 AM<br>
&gt;<br>
&gt; Sent by:<br>
&gt;<br>
&gt; <a href=3D"mailto:vwrap-bounces@ietf.org" target=3D"_blank">vwrap-boun=
ces@ietf.org</a><br>
&gt;<br>
&gt; Cc:<br>
&gt;<br>
&gt; vwrap<br>
&gt;<br>
&gt; In the spirit of good layering, it seems like we should be talking<br>
&gt; about avoiding direct reliance on IP addresses instead of how we can<b=
r>
&gt; accommodate different addresses in the protocol. =A0Why is there ever =
a<br>
&gt; need to carry an IP address in this application-layer protocol, as<br>
&gt; opposed to, say, a DNS name or a URI?<br>
&gt;<br>
&gt; --Richard<br>
&gt;<br>
+1<br>
<br>
We may from time to time have a IP address stuck in the form of a URI<br>
which has the dotted decimal form of an resource. The spec should make<br>
sure that form can be an IPV6 address, but that should be very straight<br>
forward.<br>
<br>
There may be some IPV6 features which eventually impact us at the protocol<=
br>
design level, but the entire VWRAP specification has been written in terms =
of<br>
URIs and Capabilities, not in terms of low level IP addresses. It would tak=
e an<br>
incredibly powerful argument to suggest that this should change. Likewise, =
while<br>
IPV6 changes addressing at the bottom of the stack, it doesn&#39;t apprecia=
bly change<br>
the cost of holding open sessions, of managing sockets and buffers inside o=
f<br>
clients (especially lightweight devices) Further while we can all devoutly =
hope<br>
that IPV6 finally deploys broadly, making it a dependancy in the near term =
feels<br>
rather like a roadblock to possible adoption.<br>
<br>
- David<br>
~ Zha<br>
<br>
<br>
<br>
&gt;<br>
&gt; On May 14, 2010, at 7:32 AM, Morgaine wrote:<br>
&gt;<br>
&gt; &gt; Despite exceedingly low takeup of IPv6 so far, it&#39;s coming, a=
nd in<br>
&gt; &gt; the context of IETF WG rates of progress, it is really imminent. =
=A0Of<br>
&gt; &gt; special relevance to us is that IPv4 addresses are projected to r=
un<br>
&gt; &gt; out within roughly the same time frame as VWRAP materializes.<br>
&gt; &gt;<br>
&gt; &gt; There is little point in creating a new VW protocol today purely =
in<br>
&gt; &gt; the context of IPv4 without thinking about tomorrow&#39;s IPv6<br=
>
&gt; &gt; environment. =A0By the time that VWRAP is fully defined, we shoul=
d<br>
&gt; &gt; expect a substantial and rapidly increasing proportion of VWRAP<b=
r>
&gt; &gt; implementations to occur in IPv6-accessible worlds. =A0This is a<=
br>
&gt; &gt; situation for which we need to plan now, otherwise the protocol w=
ill<br>
&gt; &gt; be obsolete before it&#39;s even ready.<br>
&gt; &gt;<br>
&gt; &gt; To get the ball rolling, here are a few IPv6-related issues that =
we<br>
&gt; &gt; could usefully address in the group:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0=95 The 128-bit IP address of IPv6 is likely to become a c=
ommon<br>
&gt; &gt; payload, so it should be supported natively. =A0LLSD already supp=
orts<br>
&gt; &gt; one 128-bit data type of course, the UUID. =A0IPv6 addresses shou=
ld<br>
&gt; &gt; not be transported in UUID fields however, since their statistica=
l<br>
&gt; &gt; properties and semantics are totally different. =A0In any case, t=
he<br>
&gt; &gt; two spaces are disjoint so confusing them would be a mistake. =A0=
The<br>
&gt; &gt; IPv6 address seems a good candidate for its own defined type, in =
the<br>
&gt; &gt; absence of wide integers.<br>
&gt; &gt; =A0 =A0=95 The extremely large address space of IPv6 has often be=
en<br>
&gt; &gt; portrayed as allowing everything around us to have its own IP<br>
&gt; &gt; address. =A0In the context of virtual worlds, this idea can actua=
lly<br>
&gt; &gt; be put to good use, with each virtual object bearing its own IPv6=
<br>
&gt; &gt; address. =A0One candidate application for this has already been<b=
r>
&gt; &gt; described in earlier discussions --- for example, implementing<br=
>
&gt; &gt; virtual object simulation in two parts, one client-side and one<b=
r>
&gt; &gt; world-side, the two parts communicating directly. =A0IPv6 address=
ing<br>
&gt; &gt; of objects makes this relatively easy to achieve efficiently, so =
its<br>
&gt; &gt; implementation in IPv6-based worlds is almost inevitable before<b=
r>
&gt; &gt; long. =A0VWRAP should be ready for this.<br>
&gt; &gt; =A0 =A0=95 The event queue in current implementations provides an=
 indirect<br>
&gt; &gt; and highly inefficient way of achieving world-to-client<br>
&gt; &gt; communications. =A0IPv6 offers opportunities for direct communica=
tion<br>
&gt; &gt; that can make the event queue approach obsolete, so it&#39;s wort=
h<br>
&gt; &gt; examining IPv6-oriented alternatives.<br>
&gt; &gt; =A0 =A0=95 We recently discussed feature and protocol negotiation=
 within<br>
&gt; &gt; VWRAP. =A0IPv6 provides much opportunity for new features and pro=
tocol<br>
&gt; &gt; pathways to be negotiated between endpoints, so it gives us a ver=
y<br>
&gt; &gt; real and imminent set of use cases for negotiation.<br>
&gt; &gt;<br>
&gt; &gt; It would also be a feather in VWRAP&#39;s cap to be considered an=
 &quot;IPv6-<br>
&gt; &gt; capable application protocol&quot; in a stronger sense than just =
to be<br>
&gt; &gt; carried by IPv6 networks. =A0IPv6 does after all bring new abilit=
ies<br>
&gt; &gt; to the table, such as the huge addressing, and it would be a mist=
ake<br>
&gt; &gt; to ignore them.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Morgaine.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; vwrap mailing list<br>
&gt; &gt; <a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.or=
g</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D=
"_blank">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; vwrap mailing list<br>
&gt; <a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
</blockquote>
<br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
</blockquote>
<br>
</div></div></blockquote></div><br>

--0016367fb68bd6204e048707a4aa--

From rbarnes@bbn.com  Thu May 20 08:19:59 2010
Return-Path: <rbarnes@bbn.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A20AD3A697B for <vwrap@core3.amsl.com>; Thu, 20 May 2010 08:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.53
X-Spam-Level: 
X-Spam-Status: No, score=-0.53 tagged_above=-999 required=5 tests=[AWL=-0.531,  BAYES_50=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 HNmTA1r-wS3R for <vwrap@core3.amsl.com>; Thu, 20 May 2010 08:19:56 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 927123A6864 for <vwrap@ietf.org>; Thu, 20 May 2010 08:19:56 -0700 (PDT)
Received: from [128.89.255.32] (port=57728 helo=[192.168.1.46]) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OF7XG-0009uL-4j; Thu, 20 May 2010 11:19:49 -0400
Message-Id: <18CBEFBB-3356-4CD0-BBFF-266672322621@bbn.com>
From: Richard Barnes <rbarnes@bbn.com>
To: Morgaine <morgaine.dinova@googlemail.com>
In-Reply-To: <AANLkTikqBQPp-o_u58tas669x55n7bZ1R3oXSoaG2q3Z@mail.gmail.com>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 20 May 2010 11:19:44 -0400
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com> <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com> <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com> <632C4898-F7DD-4B76-AAFB-D675346E2521@gmail.com> <AANLkTik42H1xhnr_yljo06-4thbaT3GcLBDabzoj2c2t@mail.gmail.com> <B2E410EF-1AD1-45E6-88A3-BE18FCC1571F@bbn.com> <AANLkTikqBQPp-o_u58tas669x55n7bZ1R3oXSoaG2q3Z@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: vwrap@ietf.org
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 15:19:59 -0000

I'm losing interest in this debate, and I think we've all said our =20
piece, so I'll just close with a reference to the venerable RFC 1958, =20=

"Architectural Principles of the Internet":
"
    In general, user applications should use names rather than =20
addresses.
"
(taken from a nice presentation that Dave Thaler gave on how =20
pathological IP addresses can be:)
<http://www.ietf.org/proceedings/73/slides/plenaryw-1.pdf>

Feel free to use IPv6 addresses in the application layer if you want, =20=

but be aware that there be dragons.

--Richard


On May 20, 2010, at 10:46 AM, Morgaine wrote:

> Abstracting over addresses is fine, Richard, but after you've dealt =20=

> with the abstractions you typically end up with addresses, and =20
> that's what protocols work with from then on.
>
> The textual abstractions are only there for human comfort, ease of =20
> configuration, and great flexibility of indirection, but =20
> abstractions are just means to an end.  After the address =20
> abstractions are de-abstracted, protocols work with the much more =20
> efficient binary representations.  That's practically universal.
>
> It's easy to give a practical example of such operation.  For =20
> example, consider a design in which all VW objects have two parts, =20
> an in-world object (IWO) and an in-client object (ICO), where the =20
> ICO is replicated in each client.  Let both parts be active, ie. =20
> both sides can be event generators.  It's easy for ICOs to address =20
> update events to their IWO because there is only one IWO, and access =20=

> could be optimized to network level after the de-abstraction step =20
> for efficiency.  But what about updates in the reverse direction, =20
> which is 1:N?
>
> In the typical IPv4 environment, the usual approach would be a =20
> heavily indirected one, with updates travelling through layer upon =20
> layer of middleware before reaching their target ICO.  In an IPv6 =20
> environment in which each ICO can have its own IPv6 address, there =20
> need be no middleware at all between the host kernel and the target =20=

> object.  The resulting increase in efficiency by orders of magnitude =20=

> can have major ramifications on the operation of your world and of =20
> your clients.
>
> And the cost of this massive leap in efficiency?  Merely to inform =20
> the IWO of the ICO's dynamic IPv6 network address, which borders on =20=

> the trivial.
>
> One of my main interests is VW scalability, both of worlds and of =20
> clients, and such efficiency gains are truly important.  Scaling VW =20=

> complexity and rendering of crowds or of highly detailed =20
> visualizations requires some lateral thinking and more powerful =20
> networking paradigms than we have been used to until now.  IPv6 =20
> offers some interesting solutions in that direction, and they will =20
> be used.
>
>
> Morgaine.
>
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> On Thu, May 20, 2010 at 2:43 PM, Richard Barnes <rbarnes@bbn.com> =20
> wrote:
> As an aside, there's nothing that says that subscribers have to be =20
> allocated a /64.  Some proposed addressing schemes that are more =20
> conservative (in the Asia/Pacific region IIRC) actually assign much =20=

> longer prefixes (smaller address blocks) to customers.
>
> Fine-grained addressability is not the same as fine-grained =20
> allocation of *IP* addresses. Think of it this way: HTTP has very =20
> fine-grained addressability, with individual identifier/locators for =20=

> pages, images, scripts, etc.  It's able to accomplish this not by =20
> assigning an IPv6 address to every object, but by using an =20
> application-layer identifier/locator -- namely a URL.
>
> Not using IPv6 addresses in applications is not painting oneself =20
> into an IPv4 corner, it's good protocol design following the =20
> layering model of the Internet.  (If we're using IPv4 addresses for =20=

> identifiers, we shouldn't be doing that either!)  Abstracting over =20
> IP addresses is about freeing the application from having to worry =20
> about whether its IPv4 or IPv6 or IPv10 or X.25 or whatever else at =20=

> the network layer.
>
> --Richard
>
>
>
>
> On May 20, 2010, at 9:23 AM, Morgaine wrote:
>
> On Thu, May 20, 2010 at 10:59 AM, Han Sontse =20
> <han.sontse.sl@gmail.com> wrote:
> I recognize that it is temping to take advantage of the huge address =20=

> space that IPv6 offers but my test engineer instincts tell me it is =20=

> unwise to do so.
>
>
> I too am an engineer, but solid engineering instincts do not tell us =20=

> to use only those facilities whose numbers or sizes can be tested =20
> exhaustively.  If it were so, we would not have multi-terabyte disk =20=

> drives today.
>
> The /64 minimum routable subnet of IPv6 address space was not =20
> designed as it was because people were expected to need 2^64 NIC =20
> cards in their PCs.  This immense per-user address block was created =20=

> because IPv6 designers could see beyond IPv4's use of addresses for =20=

> host interface identification, and were visionary enough to realize =20=

> that all objects could benefit from network addressability.  This =20
> also happens to be one of the key messages of REST.  Addressability =20=

> is extremely important, the finer the better, not only on the Web, =20
> and not only with URIs.
>
> With IPv6 just around the corner, I foresee such addressability at =20
> fine levels of granularity appearing in VWs relatively soon.  IPv4 =20
> worlds will have to emulate what IPv6 worlds achieve natively, and =20
> that is the right way around.  When legacy design restricts =20
> progress, the only thing it achieves is rapid obsolescence.
>
> I would prefer VWRAP not to be painting itself into an IPv4 corner =20
> of obsolescence before it's even released, which is why I'm raising =20=

> this topic --- it's intended as a heads-up for the group.
>
> Since the rise of VWs and IPv6 take-up are going to occur =20
> concurrently, I think the next few years are going to be very =20
> interesting on the VW networking front.  My recommendation is to =20
> observe carefully what happens, and not to make any rash decisions =20
> based on legacy ideas that could cut off your future.
>
>
> Morgaine.
>
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> On Thu, May 20, 2010 at 10:59 AM, Han Sontse =20
> <han.sontse.sl@gmail.com> wrote:
> It's a bad idea to use IP addresses for anything other than =20
> addressing a machine level interface.  Using them to interface =20
> objects at or above the application level is asking for trouble.   =20
> UUIDs are UUIDs... IP addresses are IP addresses.   The two should =20
> not be mixed.   I recognize that it is temping to take advantage of =20=

> the huge address space that IPv6 offers but my test engineer =20
> instincts tell me it is unwise to do so.
>
> Han.
>
> On May 20, 2010, at 2:50 AM, Morgaine wrote:
>
> A /64 is the smallest routable IPv6 subnet, hence there is no extra =20=

> routing overhead for the 2^(128-64) addresses in the basic block =20
> that every user will have allocated.
>
> Needless to say, there won't be anything like 2^64 objects in your =20
> scenegraph, so if you use your IPv6 address space to address every =20
> scenegraph object that you have instantiated client-side, you will =20
> still have an extremely sparsely used /64 block.  You'll be keeping =20=

> track of which addresses you have assigned dynamically of course. =20
> (An address space of this size is not linearly scannable in =20
> realistic time.)
>
> In principle this is no different to using UUIDs --- your IPv6 micro-=20=

> servers will have unguessable IPv6 addresses within your /64 block, =20=

> and it'll be up to you to tell other participants in the protocol =20
> (for example server-side objects) with which of your IPv6 micro-=20
> servers they are to communicate.  This is why an ADT that is =20
> supportive of IPv6 operation needs to be able to carry such data =20
> efficiently --- the UUID is no longer the only 128-bit datum of =20
> interest.
>
> Of course your entire /64 block is routed as one, since there are no =20=

> smaller routable subnets in IPv6, and therefore your objections =20
> about routing non-scalability do not apply.
>
>
> Morgaine.
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> On Wed, May 19, 2010 at 10:56 PM, Richard Barnes <rbarnes@bbn.com> =20
> wrote:
> The impact of IPv6 on VWs should be far less than you imagine, I =20
> think. :)
>
> It has often been said that many, many things will be assigned IPv6 =20=

> addresses.  There will certainly be enough to go around, but that =20
> doesn't make them good application-layer identifiers.  If you want =20
> to use IP addresses with IP, they have to route, and that means that =20=

> they have to be either (1) topologically assigned, or (2) overlay =20
> routed, e.g., with mobile IP.  So if you want to use an IP address =20
> to address something, you're going to have to either change that =20
> address when the thing gets connected differently, or you'll need =20
> some overlay routing scheme to route to a persistent address.  (And =20=

> if you're not going to use the address with IP, then why would you =20
> use an IP address?)
>
> VWRAP, as an application layer protocol, has a choice about what =20
> identifiers to use for things and how to use those identifiers.  =20
> ISTM that using IP addresses (again, of either type) remains a bad =20
> idea, compared with something that is decoupled from the routing =20
> layer.
>
> As far as the DNS, I'm not sure what your point is:
> (i) DNS caching has been around for decades
> (ii) DNS names can already refer to multiple addresses
> (iii) Depends on implementation.  Maybe there's some application-=20
> layer way to resolve names.  E.g., SIP endpoints don't need to have =20=

> DNS records because the INVITE transaction maps from SIP URIs to IP =20=

> addresses.
> (iv) =46rom RFC 4291: "IPv6 addresses are 128-bit identifiers for =20
> interfaces and sets of
> interfaces"
> (v) Seems like there's a use case lurking, hard to address without =20
> details.  But you're probably still at the application layer.  For =20
> instance, if you were telling your peer to send you an HTTP request, =20=

> you would send an HTTP URI, which can already handle IPv6 addresses.
>
> --Richard
>
>
>
> On May 19, 2010, at 9:35 AM, Morgaine wrote:
>
> The impact of IPv6 on VWs is going to be far greater than you =20
> imagine, I believe.  As things stand, VWRAP is being designed around =20=

> the features and limitations of IPv4 networking.  It will of course =20=

> be able to ride on top of IPv6 as a transport, but unable to benefit =20=

> from its improved feature set, unless we provide the means to do so.
>
> The question "Why is there ever a need to carry an IP address in =20
> this application-layer protocol, as opposed to, say, a DNS name or a =20=

> URI?" suggests an IPv4 mindset, because in IPv6 it has a variety of =20=

> possible answers:  (i) When the DNS lookup has already been done and =20=

> does not need to be done again, (ii) When a FQDN maps to multiple =20
> addresses, but you want to refer to a specific one, (iii) When an =20
> IPv6 address does not have an external address record, (iv) When the =20=

> host is already known and the IP address denotes something other =20
> than a physical NIC interface, or (v) When listeners are allocated =20
> locally and dynamically for the current session only, and their IP =20
> addresses need to be communicated to a peer --- this will be an =20
> extremely common use case with IPv6.
>
> In today's IPv4-based systems, it is normal for a user's machine to =20=

> have a single IP address, and for a client on that machine to talk =20
> to a server that has a single customer-facing IP address too =20
> (although it may also have others that are not public).  In IPv6-=20
> based systems, this simple scenario is still possible but represents =20=

> only a special case among a new and vastly expanded set of IPv6 use =20=

> cases.
>
> The smallest allocatable block of IPv6 address space is a /64, so =20
> 2^(128-64) IP addresses is the number that most normal IPv6 users =20
> will have, although the much larger /48 blocks of 2^80 addresses are =20=

> commonly assigned to users as well.  With such IP riches client-=20
> side, it is certain that they will be used for something, and the =20
> obvious suggestion is to give every VW object an IPv6 address of its =20=

> own.
>
> Lest we forget, one of the most important properties of the REST =20
> paradigm is addressability, but the benefits of high addressability =20=

> go far beyond the Web.  This is a property that will become =20
> ubiquitous throughout networked computing with IPv6.  It's probably =20=

> no exaggeration to say that *everything* will be getting its own IP =20=

> address. :-)
>
> Faced with that future, it's a mistake to think in IPv4 terms and =20
> consider IPv6 addresses as merely denoting a host which can be =20
> obtained from its FQDN.  That's IPv4 thinking, and represents only a =20=

> very basic use case for IPv6.  In more extended use cases, IPv6 =20
> addresses will become much more like active local UUIDs than like =20
> today's host IP addresses.  They will be used for inner-application =20=

> addressing, for example to make every object in an application an =20
> addressable micro-server.
>
> VWRAP is being born into an IPv6 world, and it would be a mistake to =20=

> hardwire IPv4 thinking into its design.  We continually refer to the =20=

> need for extensibility and a desire to future-proof the protocol, =20
> but lip service is not enough.  Adding IPv6 addresses to the =20
> underlying ADT would provide a bare minimum level of thinking ahead =20=

> to support VWRAP implementations that embrace large numbers of =20
> communicating objects.  (A generally extensible ADT would of course =20=

> achieve the same thing, and more.)
>
>
> Morgaine.
>
>
>
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> On Mon, May 17, 2010 at 3:50 PM, David W Levine <dwl@us.ibm.com> =20
> wrote:
>
>
> vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26 AM:
>
> > [image removed]
> >
> > Re: [vwrap] VWRAP and IPv6
> >
> > Richard Barnes
> >
> > to:
> >
> > Morgaine
> >
> > 05/17/2010 10:09 AM
> >
> > Sent by:
> >
> > vwrap-bounces@ietf.org
> >
> > Cc:
> >
> > vwrap
> >
> > In the spirit of good layering, it seems like we should be talking
> > about avoiding direct reliance on IP addresses instead of how we can
> > accommodate different addresses in the protocol.  Why is there =20
> ever a
> > need to carry an IP address in this application-layer protocol, as
> > opposed to, say, a DNS name or a URI?
> >
> > --Richard
> >
> +1
>
> We may from time to time have a IP address stuck in the form of a URI
> which has the dotted decimal form of an resource. The spec should make
> sure that form can be an IPV6 address, but that should be very =20
> straight
> forward.
>
> There may be some IPV6 features which eventually impact us at the =20
> protocol
> design level, but the entire VWRAP specification has been written in =20=

> terms of
> URIs and Capabilities, not in terms of low level IP addresses. It =20
> would take an
> incredibly powerful argument to suggest that this should change. =20
> Likewise, while
> IPV6 changes addressing at the bottom of the stack, it doesn't =20
> appreciably change
> the cost of holding open sessions, of managing sockets and buffers =20
> inside of
> clients (especially lightweight devices) Further while we can all =20
> devoutly hope
> that IPV6 finally deploys broadly, making it a dependancy in the =20
> near term feels
> rather like a roadblock to possible adoption.
>
> - David
> ~ Zha
>
>
>
> >
> > On May 14, 2010, at 7:32 AM, Morgaine wrote:
> >
> > > Despite exceedingly low takeup of IPv6 so far, it's coming, and in
> > > the context of IETF WG rates of progress, it is really =20
> imminent.  Of
> > > special relevance to us is that IPv4 addresses are projected to =20=

> run
> > > out within roughly the same time frame as VWRAP materializes.
> > >
> > > There is little point in creating a new VW protocol today purely =20=

> in
> > > the context of IPv4 without thinking about tomorrow's IPv6
> > > environment.  By the time that VWRAP is fully defined, we should
> > > expect a substantial and rapidly increasing proportion of VWRAP
> > > implementations to occur in IPv6-accessible worlds.  This is a
> > > situation for which we need to plan now, otherwise the protocol =20=

> will
> > > be obsolete before it's even ready.
> > >
> > > To get the ball rolling, here are a few IPv6-related issues that =20=

> we
> > > could usefully address in the group:
> > >
> > >    =95 The 128-bit IP address of IPv6 is likely to become a common
> > > payload, so it should be supported natively.  LLSD already =20
> supports
> > > one 128-bit data type of course, the UUID.  IPv6 addresses should
> > > not be transported in UUID fields however, since their statistical
> > > properties and semantics are totally different.  In any case, the
> > > two spaces are disjoint so confusing them would be a mistake.  The
> > > IPv6 address seems a good candidate for its own defined type, in =20=

> the
> > > absence of wide integers.
> > >    =95 The extremely large address space of IPv6 has often been
> > > portrayed as allowing everything around us to have its own IP
> > > address.  In the context of virtual worlds, this idea can actually
> > > be put to good use, with each virtual object bearing its own IPv6
> > > address.  One candidate application for this has already been
> > > described in earlier discussions --- for example, implementing
> > > virtual object simulation in two parts, one client-side and one
> > > world-side, the two parts communicating directly.  IPv6 addressing
> > > of objects makes this relatively easy to achieve efficiently, so =20=

> its
> > > implementation in IPv6-based worlds is almost inevitable before
> > > long.  VWRAP should be ready for this.
> > >    =95 The event queue in current implementations provides an =20
> indirect
> > > and highly inefficient way of achieving world-to-client
> > > communications.  IPv6 offers opportunities for direct =20
> communication
> > > that can make the event queue approach obsolete, so it's worth
> > > examining IPv6-oriented alternatives.
> > >    =95 We recently discussed feature and protocol negotiation =
within
> > > VWRAP.  IPv6 provides much opportunity for new features and =20
> protocol
> > > pathways to be negotiated between endpoints, so it gives us a very
> > > real and imminent set of use cases for negotiation.
> > >
> > > It would also be a feather in VWRAP's cap to be considered an =20
> "IPv6-
> > > capable application protocol" in a stronger sense than just to be
> > > carried by IPv6 networks.  IPv6 does after all bring new abilities
> > > to the table, such as the huge addressing, and it would be a =20
> mistake
> > > to ignore them.
> > >
> > >
> > > Morgaine.
> > >
> > >
> > >
> > > _______________________________________________
> > > vwrap mailing list
> > > vwrap@ietf.org
> > > https://www.ietf.org/mailman/listinfo/vwrap
> >
> > _______________________________________________
> > vwrap mailing list
> > vwrap@ietf.org
> > https://www.ietf.org/mailman/listinfo/vwrap
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap


From dwl@us.ibm.com  Thu May 20 08:43:32 2010
Return-Path: <dwl@us.ibm.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 728E53A69D7; Thu, 20 May 2010 08:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.331
X-Spam-Level: 
X-Spam-Status: No, score=-1.331 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_50=0.001, 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 66uHqVP6ZDjJ; Thu, 20 May 2010 08:43:28 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by core3.amsl.com (Postfix) with ESMTP id 27EB03A68EB; Thu, 20 May 2010 08:43:19 -0700 (PDT)
Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by e7.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id o4KFWXQW031501; Thu, 20 May 2010 11:32:33 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o4KFgtku2433142; Thu, 20 May 2010 11:42:56 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id o4KFgrT1030093; Thu, 20 May 2010 12:42:54 -0300
Received: from d01ml605.pok.ibm.com (d01ml605.pok.ibm.com [9.56.227.91]) by d01av02.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVin) with ESMTP id o4KFgrhs030088; Thu, 20 May 2010 12:42:53 -0300
In-Reply-To: <18CBEFBB-3356-4CD0-BBFF-266672322621@bbn.com>
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com>	<BCEC4B1A-A007-442C-A434-91EE3D0BB052@bbn.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com>	<AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com> <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com>	<AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com> <632C4898-F7DD-4B76-AAFB-D675346E2521@gmail.com>	<AANLkTik42H1xhnr_yljo06-4thbaT3GcLBDabzoj2c2t@mail.gmail.com> <B2E410EF-1AD1-45E6-88A3-BE18FCC1571F@bbn.com>	<AANLkTikqBQPp-o_u58tas669x55n7bZ1R3oXSoaG2q3Z@mail.gmail.com> <18CBEFBB-3356-4CD0-BBFF-266672322621@bbn.com>
To: Richard Barnes <rbarnes@bbn.com>
MIME-Version: 1.0
X-KeepSent: F2DCD36F:2AA51CA9-85257729:00553605; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2 HF623 January 16, 2009
Message-ID: <OFF2DCD36F.2AA51CA9-ON85257729.00553605-85257729.00565304@us.ibm.com>
From: David W Levine <dwl@us.ibm.com>
Date: Thu, 20 May 2010 11:42:53 -0400
X-MIMETrack: Serialize by Router on D01ML605/01/M/IBM(Release 8.5.1HF41 | October 22, 2009) at 05/20/2010 11:42:53, Serialize complete at 05/20/2010 11:42:53
Content-Type: multipart/alternative; boundary="=_alternative 005652F785257729_="
Cc: vwrap@ietf.org, vwrap-bounces@ietf.org
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 15:43:32 -0000

This is a multipart message in MIME format.
--=_alternative 005652F785257729_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

KzEgb24gYWxsIGNvdW50cyBoZXJlLg0KDQpUaGUgY3VycmVudCBzZXJ2aWNlIGVzdGFibGlzaG1l
bnQgcGF0dGVucyBwcm9wb3NlZCBpbiBWV1JBUCBpcyBub3Qgb25seSANCklQVjQvSVBWNiBhZ25v
c3RpYywgaXQgbGV2ZXJhZ2VzIHRoZSANCndlYiBhbmQgaW50ZXJuZXQgaW4gYW4gZXh0cmVtZWx5
IHRyYWRpdGlvbmFsIGZhc2hpb24uIE5hbWVkIHNlcnZpY2VzIGFyZSANCnJlcXVlc3QgdmlhIGEg
Y2FwYWJpbGl0eSBuYW1lIGFuZCANCnNlZWRjYXAsIGFuZCBhIFVSSSBpcyByZXR1cm5lZCwgd2l0
aCBwb3NzaWJsZSBjb250ZW50IG5lZ290aWF0aW9uIGFzIHRvIA0KZGV0YWlscy4NCg0KIFRoZSB3
aG9sZSBwb2ludCBvZiByZXR1cm5pbmcgYSBVUkkgaXMgdG8gaXNvbGF0ZSBWV1JBUCBmcm9tIHRy
YW5zcG9ydC4gDQpUaGF0IFVSSSBjb3VsZCBiaW5kIG9udG8gYW4gSFRUUChTKSBVUkwsIG9udG8N
CmFuIFhNUFAgIGVuZHBvaW50LCBvbnRvIGEgUlRQIHN0cmVhbSwgb250byBTSVAuLi4gDQoNClRo
ZSBtb3N0IGNvbW1vbiBwcm9maWxlIGZvciBzb21lIHRpbWUsIGlzIGxpa2VseSB0aGF0IG1vc3Qg
c2VydmljZXMgd2lsbCANCmJlIG9uIGJvcmluZyBVUkxzIHdpdGggYm9yaW5nIGh0dHAvaHR0cHMg
ZW5kcG9pbnRzLCB3aXRoIG5hbWVzDQp3aGljaCBiaW5kIG9udG8gYm9yaW5nIElQVjQgYWRkcmVz
c2VzLCBidXQsIGl0IHNob3VsZCBiZSB0b3RhbGx5IA0KdHJhbnNwYXJlbnQgdG8gdGhlIGhpZ2hl
ciBsZXZlbCBjb2RlIHdoZXRoZXIgdGhlIA0KbmV0d29yayBzdGFjayBpcyBWNCBvciBWNiwgb3Ig
VENQL0lQIGF0IGFsbC4gSWYgSSBoYWQgYSB2YWxpZCBVUkkgd2hpY2ggDQpib3VuZCBvbnRvIGEg
U05BIExVIDYuMiBlbmRwb2ludCwgIGFuZA0KbWF0Y2hpbmcgdHJhbnNwb3J0IHN0YWNrcywgaXQg
b3VnaHQgdG8gd29yay4gDQoNCi0gRGF2aWQNCn4gWmhhIA0KDQoNCnZ3cmFwLWJvdW5jZXNAaWV0
Zi5vcmcgd3JvdGUgb24gMDUvMjAvMjAxMCAxMToxOTo0NCBBTToNCg0KPiBbaW1hZ2UgcmVtb3Zl
ZF0gDQo+IA0KPiBSZTogW3Z3cmFwXSBWV1JBUCBhbmQgSVB2Ng0KPiANCj4gUmljaGFyZCBCYXJu
ZXMgDQo+IA0KPiB0bzoNCj4gDQo+IE1vcmdhaW5lDQo+IA0KPiAwNS8yMC8yMDEwIDExOjIwIEFN
DQo+IA0KPiBTZW50IGJ5Og0KPiANCj4gdndyYXAtYm91bmNlc0BpZXRmLm9yZw0KPiANCj4gQ2M6
DQo+IA0KPiB2d3JhcA0KPiANCj4gSSdtIGxvc2luZyBpbnRlcmVzdCBpbiB0aGlzIGRlYmF0ZSwg
YW5kIEkgdGhpbmsgd2UndmUgYWxsIHNhaWQgb3VyIA0KPiBwaWVjZSwgc28gSSdsbCBqdXN0IGNs
b3NlIHdpdGggYSByZWZlcmVuY2UgdG8gdGhlIHZlbmVyYWJsZSBSRkMgMTk1OCwgDQo+ICJBcmNo
aXRlY3R1cmFsIFByaW5jaXBsZXMgb2YgdGhlIEludGVybmV0IjoNCj4gIg0KPiAgICAgSW4gZ2Vu
ZXJhbCwgdXNlciBhcHBsaWNhdGlvbnMgc2hvdWxkIHVzZSBuYW1lcyByYXRoZXIgdGhhbiANCj4g
YWRkcmVzc2VzLg0KPiAiDQo+ICh0YWtlbiBmcm9tIGEgbmljZSBwcmVzZW50YXRpb24gdGhhdCBE
YXZlIFRoYWxlciBnYXZlIG9uIGhvdyANCj4gcGF0aG9sb2dpY2FsIElQIGFkZHJlc3NlcyBjYW4g
YmU6KQ0KPiA8aHR0cDovL3d3dy5pZXRmLm9yZy9wcm9jZWVkaW5ncy83My9zbGlkZXMvcGxlbmFy
eXctMS5wZGY+DQo+IA0KPiBGZWVsIGZyZWUgdG8gdXNlIElQdjYgYWRkcmVzc2VzIGluIHRoZSBh
cHBsaWNhdGlvbiBsYXllciBpZiB5b3Ugd2FudCwgDQo+IGJ1dCBiZSBhd2FyZSB0aGF0IHRoZXJl
IGJlIGRyYWdvbnMuDQo+IA0KPiAtLVJpY2hhcmQNCj4gDQo+IA0KPiBPbiBNYXkgMjAsIDIwMTAs
IGF0IDEwOjQ2IEFNLCBNb3JnYWluZSB3cm90ZToNCj4gDQo+ID4gQWJzdHJhY3Rpbmcgb3ZlciBh
ZGRyZXNzZXMgaXMgZmluZSwgUmljaGFyZCwgYnV0IGFmdGVyIHlvdSd2ZSBkZWFsdCANCj4gPiB3
aXRoIHRoZSBhYnN0cmFjdGlvbnMgeW91IHR5cGljYWxseSBlbmQgdXAgd2l0aCBhZGRyZXNzZXMs
IGFuZCANCj4gPiB0aGF0J3Mgd2hhdCBwcm90b2NvbHMgd29yayB3aXRoIGZyb20gdGhlbiBvbi4N
Cj4gPg0KPiA+IFRoZSB0ZXh0dWFsIGFic3RyYWN0aW9ucyBhcmUgb25seSB0aGVyZSBmb3IgaHVt
YW4gY29tZm9ydCwgZWFzZSBvZiANCj4gPiBjb25maWd1cmF0aW9uLCBhbmQgZ3JlYXQgZmxleGli
aWxpdHkgb2YgaW5kaXJlY3Rpb24sIGJ1dCANCj4gPiBhYnN0cmFjdGlvbnMgYXJlIGp1c3QgbWVh
bnMgdG8gYW4gZW5kLiAgQWZ0ZXIgdGhlIGFkZHJlc3MgDQo+ID4gYWJzdHJhY3Rpb25zIGFyZSBk
ZS1hYnN0cmFjdGVkLCBwcm90b2NvbHMgd29yayB3aXRoIHRoZSBtdWNoIG1vcmUgDQo+ID4gZWZm
aWNpZW50IGJpbmFyeSByZXByZXNlbnRhdGlvbnMuICBUaGF0J3MgcHJhY3RpY2FsbHkgdW5pdmVy
c2FsLg0KPiA+DQo+ID4gSXQncyBlYXN5IHRvIGdpdmUgYSBwcmFjdGljYWwgZXhhbXBsZSBvZiBz
dWNoIG9wZXJhdGlvbi4gIEZvciANCj4gPiBleGFtcGxlLCBjb25zaWRlciBhIGRlc2lnbiBpbiB3
aGljaCBhbGwgVlcgb2JqZWN0cyBoYXZlIHR3byBwYXJ0cywgDQo+ID4gYW4gaW4td29ybGQgb2Jq
ZWN0IChJV08pIGFuZCBhbiBpbi1jbGllbnQgb2JqZWN0IChJQ08pLCB3aGVyZSB0aGUgDQo+ID4g
SUNPIGlzIHJlcGxpY2F0ZWQgaW4gZWFjaCBjbGllbnQuICBMZXQgYm90aCBwYXJ0cyBiZSBhY3Rp
dmUsIGllLiANCj4gPiBib3RoIHNpZGVzIGNhbiBiZSBldmVudCBnZW5lcmF0b3JzLiAgSXQncyBl
YXN5IGZvciBJQ09zIHRvIGFkZHJlc3MgDQo+ID4gdXBkYXRlIGV2ZW50cyB0byB0aGVpciBJV08g
YmVjYXVzZSB0aGVyZSBpcyBvbmx5IG9uZSBJV08sIGFuZCBhY2Nlc3MgDQo+ID4gY291bGQgYmUg
b3B0aW1pemVkIHRvIG5ldHdvcmsgbGV2ZWwgYWZ0ZXIgdGhlIGRlLWFic3RyYWN0aW9uIHN0ZXAg
DQo+ID4gZm9yIGVmZmljaWVuY3kuICBCdXQgd2hhdCBhYm91dCB1cGRhdGVzIGluIHRoZSByZXZl
cnNlIGRpcmVjdGlvbiwgDQo+ID4gd2hpY2ggaXMgMTpOPw0KPiA+DQo+ID4gSW4gdGhlIHR5cGlj
YWwgSVB2NCBlbnZpcm9ubWVudCwgdGhlIHVzdWFsIGFwcHJvYWNoIHdvdWxkIGJlIGEgDQo+ID4g
aGVhdmlseSBpbmRpcmVjdGVkIG9uZSwgd2l0aCB1cGRhdGVzIHRyYXZlbGxpbmcgdGhyb3VnaCBs
YXllciB1cG9uIA0KPiA+IGxheWVyIG9mIG1pZGRsZXdhcmUgYmVmb3JlIHJlYWNoaW5nIHRoZWly
IHRhcmdldCBJQ08uICBJbiBhbiBJUHY2IA0KPiA+IGVudmlyb25tZW50IGluIHdoaWNoIGVhY2gg
SUNPIGNhbiBoYXZlIGl0cyBvd24gSVB2NiBhZGRyZXNzLCB0aGVyZSANCj4gPiBuZWVkIGJlIG5v
IG1pZGRsZXdhcmUgYXQgYWxsIGJldHdlZW4gdGhlIGhvc3Qga2VybmVsIGFuZCB0aGUgdGFyZ2V0
IA0KPiA+IG9iamVjdC4gIFRoZSByZXN1bHRpbmcgaW5jcmVhc2UgaW4gZWZmaWNpZW5jeSBieSBv
cmRlcnMgb2YgbWFnbml0dWRlIA0KPiA+IGNhbiBoYXZlIG1ham9yIHJhbWlmaWNhdGlvbnMgb24g
dGhlIG9wZXJhdGlvbiBvZiB5b3VyIHdvcmxkIGFuZCBvZiANCj4gPiB5b3VyIGNsaWVudHMuDQo+
ID4NCj4gPiBBbmQgdGhlIGNvc3Qgb2YgdGhpcyBtYXNzaXZlIGxlYXAgaW4gZWZmaWNpZW5jeT8g
IE1lcmVseSB0byBpbmZvcm0gDQo+ID4gdGhlIElXTyBvZiB0aGUgSUNPJ3MgZHluYW1pYyBJUHY2
IG5ldHdvcmsgYWRkcmVzcywgd2hpY2ggYm9yZGVycyBvbiANCj4gPiB0aGUgdHJpdmlhbC4NCj4g
Pg0KPiA+IE9uZSBvZiBteSBtYWluIGludGVyZXN0cyBpcyBWVyBzY2FsYWJpbGl0eSwgYm90aCBv
ZiB3b3JsZHMgYW5kIG9mIA0KPiA+IGNsaWVudHMsIGFuZCBzdWNoIGVmZmljaWVuY3kgZ2FpbnMg
YXJlIHRydWx5IGltcG9ydGFudC4gIFNjYWxpbmcgVlcgDQo+ID4gY29tcGxleGl0eSBhbmQgcmVu
ZGVyaW5nIG9mIGNyb3dkcyBvciBvZiBoaWdobHkgZGV0YWlsZWQgDQo+ID4gdmlzdWFsaXphdGlv
bnMgcmVxdWlyZXMgc29tZSBsYXRlcmFsIHRoaW5raW5nIGFuZCBtb3JlIHBvd2VyZnVsIA0KPiA+
IG5ldHdvcmtpbmcgcGFyYWRpZ21zIHRoYW4gd2UgaGF2ZSBiZWVuIHVzZWQgdG8gdW50aWwgbm93
LiAgSVB2NiANCj4gPiBvZmZlcnMgc29tZSBpbnRlcmVzdGluZyBzb2x1dGlvbnMgaW4gdGhhdCBk
aXJlY3Rpb24sIGFuZCB0aGV5IHdpbGwgDQo+ID4gYmUgdXNlZC4NCj4gPg0KPiA+DQo+ID4gTW9y
Z2FpbmUuDQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+ID09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT0NCj4gPg0KPiA+IE9uIFRodSwgTWF5IDIwLCAyMDEwIGF0IDI6NDMgUE0s
IFJpY2hhcmQgQmFybmVzIDxyYmFybmVzQGJibi5jb20+IA0KPiA+IHdyb3RlOg0KPiA+IEFzIGFu
IGFzaWRlLCB0aGVyZSdzIG5vdGhpbmcgdGhhdCBzYXlzIHRoYXQgc3Vic2NyaWJlcnMgaGF2ZSB0
byBiZSANCj4gPiBhbGxvY2F0ZWQgYSAvNjQuICBTb21lIHByb3Bvc2VkIGFkZHJlc3Npbmcgc2No
ZW1lcyB0aGF0IGFyZSBtb3JlIA0KPiA+IGNvbnNlcnZhdGl2ZSAoaW4gdGhlIEFzaWEvUGFjaWZp
YyByZWdpb24gSUlSQykgYWN0dWFsbHkgYXNzaWduIG11Y2ggDQo+ID4gbG9uZ2VyIHByZWZpeGVz
IChzbWFsbGVyIGFkZHJlc3MgYmxvY2tzKSB0byBjdXN0b21lcnMuDQo+ID4NCj4gPiBGaW5lLWdy
YWluZWQgYWRkcmVzc2FiaWxpdHkgaXMgbm90IHRoZSBzYW1lIGFzIGZpbmUtZ3JhaW5lZCANCj4g
PiBhbGxvY2F0aW9uIG9mICpJUCogYWRkcmVzc2VzLiBUaGluayBvZiBpdCB0aGlzIHdheTogSFRU
UCBoYXMgdmVyeSANCj4gPiBmaW5lLWdyYWluZWQgYWRkcmVzc2FiaWxpdHksIHdpdGggaW5kaXZp
ZHVhbCBpZGVudGlmaWVyL2xvY2F0b3JzIGZvciANCj4gPiBwYWdlcywgaW1hZ2VzLCBzY3JpcHRz
LCBldGMuICBJdCdzIGFibGUgdG8gYWNjb21wbGlzaCB0aGlzIG5vdCBieSANCj4gPiBhc3NpZ25p
bmcgYW4gSVB2NiBhZGRyZXNzIHRvIGV2ZXJ5IG9iamVjdCwgYnV0IGJ5IHVzaW5nIGFuIA0KPiA+
IGFwcGxpY2F0aW9uLWxheWVyIGlkZW50aWZpZXIvbG9jYXRvciAtLSBuYW1lbHkgYSBVUkwuDQo+
ID4NCj4gPiBOb3QgdXNpbmcgSVB2NiBhZGRyZXNzZXMgaW4gYXBwbGljYXRpb25zIGlzIG5vdCBw
YWludGluZyBvbmVzZWxmIA0KPiA+IGludG8gYW4gSVB2NCBjb3JuZXIsIGl0J3MgZ29vZCBwcm90
b2NvbCBkZXNpZ24gZm9sbG93aW5nIHRoZSANCj4gPiBsYXllcmluZyBtb2RlbCBvZiB0aGUgSW50
ZXJuZXQuICAoSWYgd2UncmUgdXNpbmcgSVB2NCBhZGRyZXNzZXMgZm9yIA0KPiA+IGlkZW50aWZp
ZXJzLCB3ZSBzaG91bGRuJ3QgYmUgZG9pbmcgdGhhdCBlaXRoZXIhKSAgQWJzdHJhY3Rpbmcgb3Zl
ciANCj4gPiBJUCBhZGRyZXNzZXMgaXMgYWJvdXQgZnJlZWluZyB0aGUgYXBwbGljYXRpb24gZnJv
bSBoYXZpbmcgdG8gd29ycnkgDQo+ID4gYWJvdXQgd2hldGhlciBpdHMgSVB2NCBvciBJUHY2IG9y
IElQdjEwIG9yIFguMjUgb3Igd2hhdGV2ZXIgZWxzZSBhdCANCj4gPiB0aGUgbmV0d29yayBsYXll
ci4NCj4gPg0KPiA+IC0tUmljaGFyZA0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4gT24gTWF5IDIw
LCAyMDEwLCBhdCA5OjIzIEFNLCBNb3JnYWluZSB3cm90ZToNCj4gPg0KPiA+IE9uIFRodSwgTWF5
IDIwLCAyMDEwIGF0IDEwOjU5IEFNLCBIYW4gU29udHNlIA0KPiA+IDxoYW4uc29udHNlLnNsQGdt
YWlsLmNvbT4gd3JvdGU6DQo+ID4gSSByZWNvZ25pemUgdGhhdCBpdCBpcyB0ZW1waW5nIHRvIHRh
a2UgYWR2YW50YWdlIG9mIHRoZSBodWdlIGFkZHJlc3MgDQo+ID4gc3BhY2UgdGhhdCBJUHY2IG9m
ZmVycyBidXQgbXkgdGVzdCBlbmdpbmVlciBpbnN0aW5jdHMgdGVsbCBtZSBpdCBpcyANCj4gPiB1
bndpc2UgdG8gZG8gc28uDQo+ID4NCj4gPg0KPiA+IEkgdG9vIGFtIGFuIGVuZ2luZWVyLCBidXQg
c29saWQgZW5naW5lZXJpbmcgaW5zdGluY3RzIGRvIG5vdCB0ZWxsIHVzIA0KPiA+IHRvIHVzZSBv
bmx5IHRob3NlIGZhY2lsaXRpZXMgd2hvc2UgbnVtYmVycyBvciBzaXplcyBjYW4gYmUgdGVzdGVk
IA0KPiA+IGV4aGF1c3RpdmVseS4gIElmIGl0IHdlcmUgc28sIHdlIHdvdWxkIG5vdCBoYXZlIG11
bHRpLXRlcmFieXRlIGRpc2sgDQo+ID4gZHJpdmVzIHRvZGF5Lg0KPiA+DQo+ID4gVGhlIC82NCBt
aW5pbXVtIHJvdXRhYmxlIHN1Ym5ldCBvZiBJUHY2IGFkZHJlc3Mgc3BhY2Ugd2FzIG5vdCANCj4g
PiBkZXNpZ25lZCBhcyBpdCB3YXMgYmVjYXVzZSBwZW9wbGUgd2VyZSBleHBlY3RlZCB0byBuZWVk
IDJeNjQgTklDIA0KPiA+IGNhcmRzIGluIHRoZWlyIFBDcy4gIFRoaXMgaW1tZW5zZSBwZXItdXNl
ciBhZGRyZXNzIGJsb2NrIHdhcyBjcmVhdGVkIA0KPiA+IGJlY2F1c2UgSVB2NiBkZXNpZ25lcnMg
Y291bGQgc2VlIGJleW9uZCBJUHY0J3MgdXNlIG9mIGFkZHJlc3NlcyBmb3IgDQo+ID4gaG9zdCBp
bnRlcmZhY2UgaWRlbnRpZmljYXRpb24sIGFuZCB3ZXJlIHZpc2lvbmFyeSBlbm91Z2ggdG8gcmVh
bGl6ZSANCj4gPiB0aGF0IGFsbCBvYmplY3RzIGNvdWxkIGJlbmVmaXQgZnJvbSBuZXR3b3JrIGFk
ZHJlc3NhYmlsaXR5LiAgVGhpcyANCj4gPiBhbHNvIGhhcHBlbnMgdG8gYmUgb25lIG9mIHRoZSBr
ZXkgbWVzc2FnZXMgb2YgUkVTVC4gIEFkZHJlc3NhYmlsaXR5IA0KPiA+IGlzIGV4dHJlbWVseSBp
bXBvcnRhbnQsIHRoZSBmaW5lciB0aGUgYmV0dGVyLCBub3Qgb25seSBvbiB0aGUgV2ViLCANCj4g
PiBhbmQgbm90IG9ubHkgd2l0aCBVUklzLg0KPiA+DQo+ID4gV2l0aCBJUHY2IGp1c3QgYXJvdW5k
IHRoZSBjb3JuZXIsIEkgZm9yZXNlZSBzdWNoIGFkZHJlc3NhYmlsaXR5IGF0IA0KPiA+IGZpbmUg
bGV2ZWxzIG9mIGdyYW51bGFyaXR5IGFwcGVhcmluZyBpbiBWV3MgcmVsYXRpdmVseSBzb29uLiAg
SVB2NCANCj4gPiB3b3JsZHMgd2lsbCBoYXZlIHRvIGVtdWxhdGUgd2hhdCBJUHY2IHdvcmxkcyBh
Y2hpZXZlIG5hdGl2ZWx5LCBhbmQgDQo+ID4gdGhhdCBpcyB0aGUgcmlnaHQgd2F5IGFyb3VuZC4g
IFdoZW4gbGVnYWN5IGRlc2lnbiByZXN0cmljdHMgDQo+ID4gcHJvZ3Jlc3MsIHRoZSBvbmx5IHRo
aW5nIGl0IGFjaGlldmVzIGlzIHJhcGlkIG9ic29sZXNjZW5jZS4NCj4gPg0KPiA+IEkgd291bGQg
cHJlZmVyIFZXUkFQIG5vdCB0byBiZSBwYWludGluZyBpdHNlbGYgaW50byBhbiBJUHY0IGNvcm5l
ciANCj4gPiBvZiBvYnNvbGVzY2VuY2UgYmVmb3JlIGl0J3MgZXZlbiByZWxlYXNlZCwgd2hpY2gg
aXMgd2h5IEknbSByYWlzaW5nIA0KPiA+IHRoaXMgdG9waWMgLS0tIGl0J3MgaW50ZW5kZWQgYXMg
YSBoZWFkcy11cCBmb3IgdGhlIGdyb3VwLg0KPiA+DQo+ID4gU2luY2UgdGhlIHJpc2Ugb2YgVldz
IGFuZCBJUHY2IHRha2UtdXAgYXJlIGdvaW5nIHRvIG9jY3VyIA0KPiA+IGNvbmN1cnJlbnRseSwg
SSB0aGluayB0aGUgbmV4dCBmZXcgeWVhcnMgYXJlIGdvaW5nIHRvIGJlIHZlcnkgDQo+ID4gaW50
ZXJlc3Rpbmcgb24gdGhlIFZXIG5ldHdvcmtpbmcgZnJvbnQuICBNeSByZWNvbW1lbmRhdGlvbiBp
cyB0byANCj4gPiBvYnNlcnZlIGNhcmVmdWxseSB3aGF0IGhhcHBlbnMsIGFuZCBub3QgdG8gbWFr
ZSBhbnkgcmFzaCBkZWNpc2lvbnMgDQo+ID4gYmFzZWQgb24gbGVnYWN5IGlkZWFzIHRoYXQgY291
bGQgY3V0IG9mZiB5b3VyIGZ1dHVyZS4NCj4gPg0KPiA+DQo+ID4gTW9yZ2FpbmUuDQo+ID4NCj4g
Pg0KPiA+DQo+ID4NCj4gPg0KPiA+ID09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
DQo+ID4NCj4gPiBPbiBUaHUsIE1heSAyMCwgMjAxMCBhdCAxMDo1OSBBTSwgSGFuIFNvbnRzZSAN
Cj4gPiA8aGFuLnNvbnRzZS5zbEBnbWFpbC5jb20+IHdyb3RlOg0KPiA+IEl0J3MgYSBiYWQgaWRl
YSB0byB1c2UgSVAgYWRkcmVzc2VzIGZvciBhbnl0aGluZyBvdGhlciB0aGFuIA0KPiA+IGFkZHJl
c3NpbmcgYSBtYWNoaW5lIGxldmVsIGludGVyZmFjZS4gIFVzaW5nIHRoZW0gdG8gaW50ZXJmYWNl
IA0KPiA+IG9iamVjdHMgYXQgb3IgYWJvdmUgdGhlIGFwcGxpY2F0aW9uIGxldmVsIGlzIGFza2lu
ZyBmb3IgdHJvdWJsZS4gDQo+ID4gVVVJRHMgYXJlIFVVSURzLi4uIElQIGFkZHJlc3NlcyBhcmUg
SVAgYWRkcmVzc2VzLiAgIFRoZSB0d28gc2hvdWxkIA0KPiA+IG5vdCBiZSBtaXhlZC4gICBJIHJl
Y29nbml6ZSB0aGF0IGl0IGlzIHRlbXBpbmcgdG8gdGFrZSBhZHZhbnRhZ2Ugb2YgDQo+ID4gdGhl
IGh1Z2UgYWRkcmVzcyBzcGFjZSB0aGF0IElQdjYgb2ZmZXJzIGJ1dCBteSB0ZXN0IGVuZ2luZWVy
IA0KPiA+IGluc3RpbmN0cyB0ZWxsIG1lIGl0IGlzIHVud2lzZSB0byBkbyBzby4NCj4gPg0KPiA+
IEhhbi4NCj4gPg0KPiA+IE9uIE1heSAyMCwgMjAxMCwgYXQgMjo1MCBBTSwgTW9yZ2FpbmUgd3Jv
dGU6DQo+ID4NCj4gPiBBIC82NCBpcyB0aGUgc21hbGxlc3Qgcm91dGFibGUgSVB2NiBzdWJuZXQs
IGhlbmNlIHRoZXJlIGlzIG5vIGV4dHJhIA0KPiA+IHJvdXRpbmcgb3ZlcmhlYWQgZm9yIHRoZSAy
XigxMjgtNjQpIGFkZHJlc3NlcyBpbiB0aGUgYmFzaWMgYmxvY2sgDQo+ID4gdGhhdCBldmVyeSB1
c2VyIHdpbGwgaGF2ZSBhbGxvY2F0ZWQuDQo+ID4NCj4gPiBOZWVkbGVzcyB0byBzYXksIHRoZXJl
IHdvbid0IGJlIGFueXRoaW5nIGxpa2UgMl42NCBvYmplY3RzIGluIHlvdXIgDQo+ID4gc2NlbmVn
cmFwaCwgc28gaWYgeW91IHVzZSB5b3VyIElQdjYgYWRkcmVzcyBzcGFjZSB0byBhZGRyZXNzIGV2
ZXJ5IA0KPiA+IHNjZW5lZ3JhcGggb2JqZWN0IHRoYXQgeW91IGhhdmUgaW5zdGFudGlhdGVkIGNs
aWVudC1zaWRlLCB5b3Ugd2lsbCANCj4gPiBzdGlsbCBoYXZlIGFuIGV4dHJlbWVseSBzcGFyc2Vs
eSB1c2VkIC82NCBibG9jay4gIFlvdSdsbCBiZSBrZWVwaW5nIA0KPiA+IHRyYWNrIG9mIHdoaWNo
IGFkZHJlc3NlcyB5b3UgaGF2ZSBhc3NpZ25lZCBkeW5hbWljYWxseSBvZiBjb3Vyc2UuIA0KPiA+
IChBbiBhZGRyZXNzIHNwYWNlIG9mIHRoaXMgc2l6ZSBpcyBub3QgbGluZWFybHkgc2Nhbm5hYmxl
IGluIA0KPiA+IHJlYWxpc3RpYyB0aW1lLikNCj4gPg0KPiA+IEluIHByaW5jaXBsZSB0aGlzIGlz
IG5vIGRpZmZlcmVudCB0byB1c2luZyBVVUlEcyAtLS0geW91ciBJUHY2IG1pY3JvLSANCj4gPiBz
ZXJ2ZXJzIHdpbGwgaGF2ZSB1bmd1ZXNzYWJsZSBJUHY2IGFkZHJlc3NlcyB3aXRoaW4geW91ciAv
NjQgYmxvY2ssIA0KPiA+IGFuZCBpdCdsbCBiZSB1cCB0byB5b3UgdG8gdGVsbCBvdGhlciBwYXJ0
aWNpcGFudHMgaW4gdGhlIHByb3RvY29sIA0KPiA+IChmb3IgZXhhbXBsZSBzZXJ2ZXItc2lkZSBv
YmplY3RzKSB3aXRoIHdoaWNoIG9mIHlvdXIgSVB2NiBtaWNyby0gDQo+ID4gc2VydmVycyB0aGV5
IGFyZSB0byBjb21tdW5pY2F0ZS4gIFRoaXMgaXMgd2h5IGFuIEFEVCB0aGF0IGlzIA0KPiA+IHN1
cHBvcnRpdmUgb2YgSVB2NiBvcGVyYXRpb24gbmVlZHMgdG8gYmUgYWJsZSB0byBjYXJyeSBzdWNo
IGRhdGEgDQo+ID4gZWZmaWNpZW50bHkgLS0tIHRoZSBVVUlEIGlzIG5vIGxvbmdlciB0aGUgb25s
eSAxMjgtYml0IGRhdHVtIG9mIA0KPiA+IGludGVyZXN0Lg0KPiA+DQo+ID4gT2YgY291cnNlIHlv
dXIgZW50aXJlIC82NCBibG9jayBpcyByb3V0ZWQgYXMgb25lLCBzaW5jZSB0aGVyZSBhcmUgbm8g
DQo+ID4gc21hbGxlciByb3V0YWJsZSBzdWJuZXRzIGluIElQdjYsIGFuZCB0aGVyZWZvcmUgeW91
ciBvYmplY3Rpb25zIA0KPiA+IGFib3V0IHJvdXRpbmcgbm9uLXNjYWxhYmlsaXR5IGRvIG5vdCBh
cHBseS4NCj4gPg0KPiA+DQo+ID4gTW9yZ2FpbmUuDQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPiA9
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQo+ID4NCj4gPiBPbiBXZWQsIE1h
eSAxOSwgMjAxMCBhdCAxMDo1NiBQTSwgUmljaGFyZCBCYXJuZXMgPHJiYXJuZXNAYmJuLmNvbT4g
DQo+ID4gd3JvdGU6DQo+ID4gVGhlIGltcGFjdCBvZiBJUHY2IG9uIFZXcyBzaG91bGQgYmUgZmFy
IGxlc3MgdGhhbiB5b3UgaW1hZ2luZSwgSSANCj4gPiB0aGluay4gOikNCj4gPg0KPiA+IEl0IGhh
cyBvZnRlbiBiZWVuIHNhaWQgdGhhdCBtYW55LCBtYW55IHRoaW5ncyB3aWxsIGJlIGFzc2lnbmVk
IElQdjYgDQo+ID4gYWRkcmVzc2VzLiAgVGhlcmUgd2lsbCBjZXJ0YWlubHkgYmUgZW5vdWdoIHRv
IGdvIGFyb3VuZCwgYnV0IHRoYXQgDQo+ID4gZG9lc24ndCBtYWtlIHRoZW0gZ29vZCBhcHBsaWNh
dGlvbi1sYXllciBpZGVudGlmaWVycy4gIElmIHlvdSB3YW50IA0KPiA+IHRvIHVzZSBJUCBhZGRy
ZXNzZXMgd2l0aCBJUCwgdGhleSBoYXZlIHRvIHJvdXRlLCBhbmQgdGhhdCBtZWFucyB0aGF0IA0K
PiA+IHRoZXkgaGF2ZSB0byBiZSBlaXRoZXIgKDEpIHRvcG9sb2dpY2FsbHkgYXNzaWduZWQsIG9y
ICgyKSBvdmVybGF5IA0KPiA+IHJvdXRlZCwgZS5nLiwgd2l0aCBtb2JpbGUgSVAuICBTbyBpZiB5
b3Ugd2FudCB0byB1c2UgYW4gSVAgYWRkcmVzcyANCj4gPiB0byBhZGRyZXNzIHNvbWV0aGluZywg
eW91J3JlIGdvaW5nIHRvIGhhdmUgdG8gZWl0aGVyIGNoYW5nZSB0aGF0IA0KPiA+IGFkZHJlc3Mg
d2hlbiB0aGUgdGhpbmcgZ2V0cyBjb25uZWN0ZWQgZGlmZmVyZW50bHksIG9yIHlvdSdsbCBuZWVk
IA0KPiA+IHNvbWUgb3ZlcmxheSByb3V0aW5nIHNjaGVtZSB0byByb3V0ZSB0byBhIHBlcnNpc3Rl
bnQgYWRkcmVzcy4gIChBbmQgDQo+ID4gaWYgeW91J3JlIG5vdCBnb2luZyB0byB1c2UgdGhlIGFk
ZHJlc3Mgd2l0aCBJUCwgdGhlbiB3aHkgd291bGQgeW91IA0KPiA+IHVzZSBhbiBJUCBhZGRyZXNz
PykNCj4gPg0KPiA+IFZXUkFQLCBhcyBhbiBhcHBsaWNhdGlvbiBsYXllciBwcm90b2NvbCwgaGFz
IGEgY2hvaWNlIGFib3V0IHdoYXQgDQo+ID4gaWRlbnRpZmllcnMgdG8gdXNlIGZvciB0aGluZ3Mg
YW5kIGhvdyB0byB1c2UgdGhvc2UgaWRlbnRpZmllcnMuIA0KPiA+IElTVE0gdGhhdCB1c2luZyBJ
UCBhZGRyZXNzZXMgKGFnYWluLCBvZiBlaXRoZXIgdHlwZSkgcmVtYWlucyBhIGJhZCANCj4gPiBp
ZGVhLCBjb21wYXJlZCB3aXRoIHNvbWV0aGluZyB0aGF0IGlzIGRlY291cGxlZCBmcm9tIHRoZSBy
b3V0aW5nIA0KPiA+IGxheWVyLg0KPiA+DQo+ID4gQXMgZmFyIGFzIHRoZSBETlMsIEknbSBub3Qg
c3VyZSB3aGF0IHlvdXIgcG9pbnQgaXM6DQo+ID4gKGkpIEROUyBjYWNoaW5nIGhhcyBiZWVuIGFy
b3VuZCBmb3IgZGVjYWRlcw0KPiA+IChpaSkgRE5TIG5hbWVzIGNhbiBhbHJlYWR5IHJlZmVyIHRv
IG11bHRpcGxlIGFkZHJlc3Nlcw0KPiA+IChpaWkpIERlcGVuZHMgb24gaW1wbGVtZW50YXRpb24u
ICBNYXliZSB0aGVyZSdzIHNvbWUgYXBwbGljYXRpb24tIA0KPiA+IGxheWVyIHdheSB0byByZXNv
bHZlIG5hbWVzLiAgRS5nLiwgU0lQIGVuZHBvaW50cyBkb24ndCBuZWVkIHRvIGhhdmUgDQo+ID4g
RE5TIHJlY29yZHMgYmVjYXVzZSB0aGUgSU5WSVRFIHRyYW5zYWN0aW9uIG1hcHMgZnJvbSBTSVAg
VVJJcyB0byBJUCANCj4gPiBhZGRyZXNzZXMuDQo+ID4gKGl2KSBGcm9tIFJGQyA0MjkxOiAiSVB2
NiBhZGRyZXNzZXMgYXJlIDEyOC1iaXQgaWRlbnRpZmllcnMgZm9yIA0KPiA+IGludGVyZmFjZXMg
YW5kIHNldHMgb2YNCj4gPiBpbnRlcmZhY2VzIg0KPiA+ICh2KSBTZWVtcyBsaWtlIHRoZXJlJ3Mg
YSB1c2UgY2FzZSBsdXJraW5nLCBoYXJkIHRvIGFkZHJlc3Mgd2l0aG91dCANCj4gPiBkZXRhaWxz
LiAgQnV0IHlvdSdyZSBwcm9iYWJseSBzdGlsbCBhdCB0aGUgYXBwbGljYXRpb24gbGF5ZXIuICBG
b3IgDQo+ID4gaW5zdGFuY2UsIGlmIHlvdSB3ZXJlIHRlbGxpbmcgeW91ciBwZWVyIHRvIHNlbmQg
eW91IGFuIEhUVFAgcmVxdWVzdCwgDQo+ID4geW91IHdvdWxkIHNlbmQgYW4gSFRUUCBVUkksIHdo
aWNoIGNhbiBhbHJlYWR5IGhhbmRsZSBJUHY2IGFkZHJlc3Nlcy4NCj4gPg0KPiA+IC0tUmljaGFy
ZA0KPiA+DQo+ID4NCj4gPg0KPiA+IE9uIE1heSAxOSwgMjAxMCwgYXQgOTozNSBBTSwgTW9yZ2Fp
bmUgd3JvdGU6DQo+ID4NCj4gPiBUaGUgaW1wYWN0IG9mIElQdjYgb24gVldzIGlzIGdvaW5nIHRv
IGJlIGZhciBncmVhdGVyIHRoYW4geW91IA0KPiA+IGltYWdpbmUsIEkgYmVsaWV2ZS4gIEFzIHRo
aW5ncyBzdGFuZCwgVldSQVAgaXMgYmVpbmcgZGVzaWduZWQgYXJvdW5kIA0KPiA+IHRoZSBmZWF0
dXJlcyBhbmQgbGltaXRhdGlvbnMgb2YgSVB2NCBuZXR3b3JraW5nLiAgSXQgd2lsbCBvZiBjb3Vy
c2UgDQo+ID4gYmUgYWJsZSB0byByaWRlIG9uIHRvcCBvZiBJUHY2IGFzIGEgdHJhbnNwb3J0LCBi
dXQgdW5hYmxlIHRvIGJlbmVmaXQgDQo+ID4gZnJvbSBpdHMgaW1wcm92ZWQgZmVhdHVyZSBzZXQs
IHVubGVzcyB3ZSBwcm92aWRlIHRoZSBtZWFucyB0byBkbyBzby4NCj4gPg0KPiA+IFRoZSBxdWVz
dGlvbiAiV2h5IGlzIHRoZXJlIGV2ZXIgYSBuZWVkIHRvIGNhcnJ5IGFuIElQIGFkZHJlc3MgaW4g
DQo+ID4gdGhpcyBhcHBsaWNhdGlvbi1sYXllciBwcm90b2NvbCwgYXMgb3Bwb3NlZCB0bywgc2F5
LCBhIEROUyBuYW1lIG9yIGEgDQo+ID4gVVJJPyIgc3VnZ2VzdHMgYW4gSVB2NCBtaW5kc2V0LCBi
ZWNhdXNlIGluIElQdjYgaXQgaGFzIGEgdmFyaWV0eSBvZiANCj4gPiBwb3NzaWJsZSBhbnN3ZXJz
OiAgKGkpIFdoZW4gdGhlIEROUyBsb29rdXAgaGFzIGFscmVhZHkgYmVlbiBkb25lIGFuZCANCj4g
PiBkb2VzIG5vdCBuZWVkIHRvIGJlIGRvbmUgYWdhaW4sIChpaSkgV2hlbiBhIEZRRE4gbWFwcyB0
byBtdWx0aXBsZSANCj4gPiBhZGRyZXNzZXMsIGJ1dCB5b3Ugd2FudCB0byByZWZlciB0byBhIHNw
ZWNpZmljIG9uZSwgKGlpaSkgV2hlbiBhbiANCj4gPiBJUHY2IGFkZHJlc3MgZG9lcyBub3QgaGF2
ZSBhbiBleHRlcm5hbCBhZGRyZXNzIHJlY29yZCwgKGl2KSBXaGVuIHRoZSANCj4gPiBob3N0IGlz
IGFscmVhZHkga25vd24gYW5kIHRoZSBJUCBhZGRyZXNzIGRlbm90ZXMgc29tZXRoaW5nIG90aGVy
IA0KPiA+IHRoYW4gYSBwaHlzaWNhbCBOSUMgaW50ZXJmYWNlLCBvciAodikgV2hlbiBsaXN0ZW5l
cnMgYXJlIGFsbG9jYXRlZCANCj4gPiBsb2NhbGx5IGFuZCBkeW5hbWljYWxseSBmb3IgdGhlIGN1
cnJlbnQgc2Vzc2lvbiBvbmx5LCBhbmQgdGhlaXIgSVAgDQo+ID4gYWRkcmVzc2VzIG5lZWQgdG8g
YmUgY29tbXVuaWNhdGVkIHRvIGEgcGVlciAtLS0gdGhpcyB3aWxsIGJlIGFuIA0KPiA+IGV4dHJl
bWVseSBjb21tb24gdXNlIGNhc2Ugd2l0aCBJUHY2Lg0KPiA+DQo+ID4gSW4gdG9kYXkncyBJUHY0
LWJhc2VkIHN5c3RlbXMsIGl0IGlzIG5vcm1hbCBmb3IgYSB1c2VyJ3MgbWFjaGluZSB0byANCj4g
PiBoYXZlIGEgc2luZ2xlIElQIGFkZHJlc3MsIGFuZCBmb3IgYSBjbGllbnQgb24gdGhhdCBtYWNo
aW5lIHRvIHRhbGsgDQo+ID4gdG8gYSBzZXJ2ZXIgdGhhdCBoYXMgYSBzaW5nbGUgY3VzdG9tZXIt
ZmFjaW5nIElQIGFkZHJlc3MgdG9vIA0KPiA+IChhbHRob3VnaCBpdCBtYXkgYWxzbyBoYXZlIG90
aGVycyB0aGF0IGFyZSBub3QgcHVibGljKS4gIEluIElQdjYtIA0KPiA+IGJhc2VkIHN5c3RlbXMs
IHRoaXMgc2ltcGxlIHNjZW5hcmlvIGlzIHN0aWxsIHBvc3NpYmxlIGJ1dCByZXByZXNlbnRzIA0K
PiA+IG9ubHkgYSBzcGVjaWFsIGNhc2UgYW1vbmcgYSBuZXcgYW5kIHZhc3RseSBleHBhbmRlZCBz
ZXQgb2YgSVB2NiB1c2UgDQo+ID4gY2FzZXMuDQo+ID4NCj4gPiBUaGUgc21hbGxlc3QgYWxsb2Nh
dGFibGUgYmxvY2sgb2YgSVB2NiBhZGRyZXNzIHNwYWNlIGlzIGEgLzY0LCBzbyANCj4gPiAyXigx
MjgtNjQpIElQIGFkZHJlc3NlcyBpcyB0aGUgbnVtYmVyIHRoYXQgbW9zdCBub3JtYWwgSVB2NiB1
c2VycyANCj4gPiB3aWxsIGhhdmUsIGFsdGhvdWdoIHRoZSBtdWNoIGxhcmdlciAvNDggYmxvY2tz
IG9mIDJeODAgYWRkcmVzc2VzIGFyZSANCj4gPiBjb21tb25seSBhc3NpZ25lZCB0byB1c2VycyBh
cyB3ZWxsLiAgV2l0aCBzdWNoIElQIHJpY2hlcyBjbGllbnQtIA0KPiA+IHNpZGUsIGl0IGlzIGNl
cnRhaW4gdGhhdCB0aGV5IHdpbGwgYmUgdXNlZCBmb3Igc29tZXRoaW5nLCBhbmQgdGhlIA0KPiA+
IG9idmlvdXMgc3VnZ2VzdGlvbiBpcyB0byBnaXZlIGV2ZXJ5IFZXIG9iamVjdCBhbiBJUHY2IGFk
ZHJlc3Mgb2YgaXRzIA0KPiA+IG93bi4NCj4gPg0KPiA+IExlc3Qgd2UgZm9yZ2V0LCBvbmUgb2Yg
dGhlIG1vc3QgaW1wb3J0YW50IHByb3BlcnRpZXMgb2YgdGhlIFJFU1QgDQo+ID4gcGFyYWRpZ20g
aXMgYWRkcmVzc2FiaWxpdHksIGJ1dCB0aGUgYmVuZWZpdHMgb2YgaGlnaCBhZGRyZXNzYWJpbGl0
eSANCj4gPiBnbyBmYXIgYmV5b25kIHRoZSBXZWIuICBUaGlzIGlzIGEgcHJvcGVydHkgdGhhdCB3
aWxsIGJlY29tZSANCj4gPiB1YmlxdWl0b3VzIHRocm91Z2hvdXQgbmV0d29ya2VkIGNvbXB1dGlu
ZyB3aXRoIElQdjYuICBJdCdzIHByb2JhYmx5IA0KPiA+IG5vIGV4YWdnZXJhdGlvbiB0byBzYXkg
dGhhdCAqZXZlcnl0aGluZyogd2lsbCBiZSBnZXR0aW5nIGl0cyBvd24gSVAgDQo+ID4gYWRkcmVz
cy4gOi0pDQo+ID4NCj4gPiBGYWNlZCB3aXRoIHRoYXQgZnV0dXJlLCBpdCdzIGEgbWlzdGFrZSB0
byB0aGluayBpbiBJUHY0IHRlcm1zIGFuZCANCj4gPiBjb25zaWRlciBJUHY2IGFkZHJlc3NlcyBh
cyBtZXJlbHkgZGVub3RpbmcgYSBob3N0IHdoaWNoIGNhbiBiZSANCj4gPiBvYnRhaW5lZCBmcm9t
IGl0cyBGUUROLiAgVGhhdCdzIElQdjQgdGhpbmtpbmcsIGFuZCByZXByZXNlbnRzIG9ubHkgYSAN
Cj4gPiB2ZXJ5IGJhc2ljIHVzZSBjYXNlIGZvciBJUHY2LiAgSW4gbW9yZSBleHRlbmRlZCB1c2Ug
Y2FzZXMsIElQdjYgDQo+ID4gYWRkcmVzc2VzIHdpbGwgYmVjb21lIG11Y2ggbW9yZSBsaWtlIGFj
dGl2ZSBsb2NhbCBVVUlEcyB0aGFuIGxpa2UgDQo+ID4gdG9kYXkncyBob3N0IElQIGFkZHJlc3Nl
cy4gIFRoZXkgd2lsbCBiZSB1c2VkIGZvciBpbm5lci1hcHBsaWNhdGlvbiANCj4gPiBhZGRyZXNz
aW5nLCBmb3IgZXhhbXBsZSB0byBtYWtlIGV2ZXJ5IG9iamVjdCBpbiBhbiBhcHBsaWNhdGlvbiBh
biANCj4gPiBhZGRyZXNzYWJsZSBtaWNyby1zZXJ2ZXIuDQo+ID4NCj4gPiBWV1JBUCBpcyBiZWlu
ZyBib3JuIGludG8gYW4gSVB2NiB3b3JsZCwgYW5kIGl0IHdvdWxkIGJlIGEgbWlzdGFrZSB0byAN
Cj4gPiBoYXJkd2lyZSBJUHY0IHRoaW5raW5nIGludG8gaXRzIGRlc2lnbi4gIFdlIGNvbnRpbnVh
bGx5IHJlZmVyIHRvIHRoZSANCj4gPiBuZWVkIGZvciBleHRlbnNpYmlsaXR5IGFuZCBhIGRlc2ly
ZSB0byBmdXR1cmUtcHJvb2YgdGhlIHByb3RvY29sLCANCj4gPiBidXQgbGlwIHNlcnZpY2UgaXMg
bm90IGVub3VnaC4gIEFkZGluZyBJUHY2IGFkZHJlc3NlcyB0byB0aGUgDQo+ID4gdW5kZXJseWlu
ZyBBRFQgd291bGQgcHJvdmlkZSBhIGJhcmUgbWluaW11bSBsZXZlbCBvZiB0aGlua2luZyBhaGVh
ZCANCj4gPiB0byBzdXBwb3J0IFZXUkFQIGltcGxlbWVudGF0aW9ucyB0aGF0IGVtYnJhY2UgbGFy
Z2UgbnVtYmVycyBvZiANCj4gPiBjb21tdW5pY2F0aW5nIG9iamVjdHMuICAoQSBnZW5lcmFsbHkg
ZXh0ZW5zaWJsZSBBRFQgd291bGQgb2YgY291cnNlIA0KPiA+IGFjaGlldmUgdGhlIHNhbWUgdGhp
bmcsIGFuZCBtb3JlLikNCj4gPg0KPiA+DQo+ID4gTW9yZ2FpbmUuDQo+ID4NCj4gPg0KPiA+DQo+
ID4NCj4gPg0KPiA+DQo+ID4NCj4gPiA9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09DQo+ID4NCj4gPiBPbiBNb24sIE1heSAxNywgMjAxMCBhdCAzOjUwIFBNLCBE
YXZpZCBXIExldmluZSA8ZHdsQHVzLmlibS5jb20+IA0KPiA+IHdyb3RlOg0KPiA+DQo+ID4NCj4g
PiB2d3JhcC1ib3VuY2VzQGlldGYub3JnIHdyb3RlIG9uIDA1LzE3LzIwMTAgMTA6MDg6MjYgQU06
DQo+ID4NCj4gPiA+IFtpbWFnZSByZW1vdmVkXQ0KPiA+ID4NCj4gPiA+IFJlOiBbdndyYXBdIFZX
UkFQIGFuZCBJUHY2DQo+ID4gPg0KPiA+ID4gUmljaGFyZCBCYXJuZXMNCj4gPiA+DQo+ID4gPiB0
bzoNCj4gPiA+DQo+ID4gPiBNb3JnYWluZQ0KPiA+ID4NCj4gPiA+IDA1LzE3LzIwMTAgMTA6MDkg
QU0NCj4gPiA+DQo+ID4gPiBTZW50IGJ5Og0KPiA+ID4NCj4gPiA+IHZ3cmFwLWJvdW5jZXNAaWV0
Zi5vcmcNCj4gPiA+DQo+ID4gPiBDYzoNCj4gPiA+DQo+ID4gPiB2d3JhcA0KPiA+ID4NCj4gPiA+
IEluIHRoZSBzcGlyaXQgb2YgZ29vZCBsYXllcmluZywgaXQgc2VlbXMgbGlrZSB3ZSBzaG91bGQg
YmUgdGFsa2luZw0KPiA+ID4gYWJvdXQgYXZvaWRpbmcgZGlyZWN0IHJlbGlhbmNlIG9uIElQIGFk
ZHJlc3NlcyBpbnN0ZWFkIG9mIGhvdyB3ZSBjYW4NCj4gPiA+IGFjY29tbW9kYXRlIGRpZmZlcmVu
dCBhZGRyZXNzZXMgaW4gdGhlIHByb3RvY29sLiAgV2h5IGlzIHRoZXJlIA0KPiA+IGV2ZXIgYQ0K
PiA+ID4gbmVlZCB0byBjYXJyeSBhbiBJUCBhZGRyZXNzIGluIHRoaXMgYXBwbGljYXRpb24tbGF5
ZXIgcHJvdG9jb2wsIGFzDQo+ID4gPiBvcHBvc2VkIHRvLCBzYXksIGEgRE5TIG5hbWUgb3IgYSBV
Ukk/DQo+ID4gPg0KPiA+ID4gLS1SaWNoYXJkDQo+ID4gPg0KPiA+ICsxDQo+ID4NCj4gPiBXZSBt
YXkgZnJvbSB0aW1lIHRvIHRpbWUgaGF2ZSBhIElQIGFkZHJlc3Mgc3R1Y2sgaW4gdGhlIGZvcm0g
b2YgYSBVUkkNCj4gPiB3aGljaCBoYXMgdGhlIGRvdHRlZCBkZWNpbWFsIGZvcm0gb2YgYW4gcmVz
b3VyY2UuIFRoZSBzcGVjIHNob3VsZCBtYWtlDQo+ID4gc3VyZSB0aGF0IGZvcm0gY2FuIGJlIGFu
IElQVjYgYWRkcmVzcywgYnV0IHRoYXQgc2hvdWxkIGJlIHZlcnkgDQo+ID4gc3RyYWlnaHQNCj4g
PiBmb3J3YXJkLg0KPiA+DQo+ID4gVGhlcmUgbWF5IGJlIHNvbWUgSVBWNiBmZWF0dXJlcyB3aGlj
aCBldmVudHVhbGx5IGltcGFjdCB1cyBhdCB0aGUgDQo+ID4gcHJvdG9jb2wNCj4gPiBkZXNpZ24g
bGV2ZWwsIGJ1dCB0aGUgZW50aXJlIFZXUkFQIHNwZWNpZmljYXRpb24gaGFzIGJlZW4gd3JpdHRl
biBpbiANCj4gPiB0ZXJtcyBvZg0KPiA+IFVSSXMgYW5kIENhcGFiaWxpdGllcywgbm90IGluIHRl
cm1zIG9mIGxvdyBsZXZlbCBJUCBhZGRyZXNzZXMuIEl0IA0KPiA+IHdvdWxkIHRha2UgYW4NCj4g
PiBpbmNyZWRpYmx5IHBvd2VyZnVsIGFyZ3VtZW50IHRvIHN1Z2dlc3QgdGhhdCB0aGlzIHNob3Vs
ZCBjaGFuZ2UuIA0KPiA+IExpa2V3aXNlLCB3aGlsZQ0KPiA+IElQVjYgY2hhbmdlcyBhZGRyZXNz
aW5nIGF0IHRoZSBib3R0b20gb2YgdGhlIHN0YWNrLCBpdCBkb2Vzbid0IA0KPiA+IGFwcHJlY2lh
Ymx5IGNoYW5nZQ0KPiA+IHRoZSBjb3N0IG9mIGhvbGRpbmcgb3BlbiBzZXNzaW9ucywgb2YgbWFu
YWdpbmcgc29ja2V0cyBhbmQgYnVmZmVycyANCj4gPiBpbnNpZGUgb2YNCj4gPiBjbGllbnRzIChl
c3BlY2lhbGx5IGxpZ2h0d2VpZ2h0IGRldmljZXMpIEZ1cnRoZXIgd2hpbGUgd2UgY2FuIGFsbCAN
Cj4gPiBkZXZvdXRseSBob3BlDQo+ID4gdGhhdCBJUFY2IGZpbmFsbHkgZGVwbG95cyBicm9hZGx5
LCBtYWtpbmcgaXQgYSBkZXBlbmRhbmN5IGluIHRoZSANCj4gPiBuZWFyIHRlcm0gZmVlbHMNCj4g
PiByYXRoZXIgbGlrZSBhIHJvYWRibG9jayB0byBwb3NzaWJsZSBhZG9wdGlvbi4NCj4gPg0KPiA+
IC0gRGF2aWQNCj4gPiB+IFpoYQ0KPiA+DQo+ID4NCj4gPg0KPiA+ID4NCj4gPiA+IE9uIE1heSAx
NCwgMjAxMCwgYXQgNzozMiBBTSwgTW9yZ2FpbmUgd3JvdGU6DQo+ID4gPg0KPiA+ID4gPiBEZXNw
aXRlIGV4Y2VlZGluZ2x5IGxvdyB0YWtldXAgb2YgSVB2NiBzbyBmYXIsIGl0J3MgY29taW5nLCBh
bmQgaW4NCj4gPiA+ID4gdGhlIGNvbnRleHQgb2YgSUVURiBXRyByYXRlcyBvZiBwcm9ncmVzcywg
aXQgaXMgcmVhbGx5IA0KPiA+IGltbWluZW50LiAgT2YNCj4gPiA+ID4gc3BlY2lhbCByZWxldmFu
Y2UgdG8gdXMgaXMgdGhhdCBJUHY0IGFkZHJlc3NlcyBhcmUgcHJvamVjdGVkIHRvIA0KPiA+IHJ1
bg0KPiA+ID4gPiBvdXQgd2l0aGluIHJvdWdobHkgdGhlIHNhbWUgdGltZSBmcmFtZSBhcyBWV1JB
UCBtYXRlcmlhbGl6ZXMuDQo+ID4gPiA+DQo+ID4gPiA+IFRoZXJlIGlzIGxpdHRsZSBwb2ludCBp
biBjcmVhdGluZyBhIG5ldyBWVyBwcm90b2NvbCB0b2RheSBwdXJlbHkgDQo+ID4gaW4NCj4gPiA+
ID4gdGhlIGNvbnRleHQgb2YgSVB2NCB3aXRob3V0IHRoaW5raW5nIGFib3V0IHRvbW9ycm93J3Mg
SVB2Ng0KPiA+ID4gPiBlbnZpcm9ubWVudC4gIEJ5IHRoZSB0aW1lIHRoYXQgVldSQVAgaXMgZnVs
bHkgZGVmaW5lZCwgd2Ugc2hvdWxkDQo+ID4gPiA+IGV4cGVjdCBhIHN1YnN0YW50aWFsIGFuZCBy
YXBpZGx5IGluY3JlYXNpbmcgcHJvcG9ydGlvbiBvZiBWV1JBUA0KPiA+ID4gPiBpbXBsZW1lbnRh
dGlvbnMgdG8gb2NjdXIgaW4gSVB2Ni1hY2Nlc3NpYmxlIHdvcmxkcy4gIFRoaXMgaXMgYQ0KPiA+
ID4gPiBzaXR1YXRpb24gZm9yIHdoaWNoIHdlIG5lZWQgdG8gcGxhbiBub3csIG90aGVyd2lzZSB0
aGUgcHJvdG9jb2wgDQo+ID4gd2lsbA0KPiA+ID4gPiBiZSBvYnNvbGV0ZSBiZWZvcmUgaXQncyBl
dmVuIHJlYWR5Lg0KPiA+ID4gPg0KPiA+ID4gPiBUbyBnZXQgdGhlIGJhbGwgcm9sbGluZywgaGVy
ZSBhcmUgYSBmZXcgSVB2Ni1yZWxhdGVkIGlzc3VlcyB0aGF0IA0KPiA+IHdlDQo+ID4gPiA+IGNv
dWxkIHVzZWZ1bGx5IGFkZHJlc3MgaW4gdGhlIGdyb3VwOg0KPiA+ID4gPg0KPiA+ID4gPiAgICDi
gKIgVGhlIDEyOC1iaXQgSVAgYWRkcmVzcyBvZiBJUHY2IGlzIGxpa2VseSB0byBiZWNvbWUgYSBj
b21tb24NCj4gPiA+ID4gcGF5bG9hZCwgc28gaXQgc2hvdWxkIGJlIHN1cHBvcnRlZCBuYXRpdmVs
eS4gIExMU0QgYWxyZWFkeSANCj4gPiBzdXBwb3J0cw0KPiA+ID4gPiBvbmUgMTI4LWJpdCBkYXRh
IHR5cGUgb2YgY291cnNlLCB0aGUgVVVJRC4gIElQdjYgYWRkcmVzc2VzIHNob3VsZA0KPiA+ID4g
PiBub3QgYmUgdHJhbnNwb3J0ZWQgaW4gVVVJRCBmaWVsZHMgaG93ZXZlciwgc2luY2UgdGhlaXIg
c3RhdGlzdGljYWwNCj4gPiA+ID4gcHJvcGVydGllcyBhbmQgc2VtYW50aWNzIGFyZSB0b3RhbGx5
IGRpZmZlcmVudC4gIEluIGFueSBjYXNlLCB0aGUNCj4gPiA+ID4gdHdvIHNwYWNlcyBhcmUgZGlz
am9pbnQgc28gY29uZnVzaW5nIHRoZW0gd291bGQgYmUgYSBtaXN0YWtlLiAgVGhlDQo+ID4gPiA+
IElQdjYgYWRkcmVzcyBzZWVtcyBhIGdvb2QgY2FuZGlkYXRlIGZvciBpdHMgb3duIGRlZmluZWQg
dHlwZSwgaW4gDQo+ID4gdGhlDQo+ID4gPiA+IGFic2VuY2Ugb2Ygd2lkZSBpbnRlZ2Vycy4NCj4g
PiA+ID4gICAg4oCiIFRoZSBleHRyZW1lbHkgbGFyZ2UgYWRkcmVzcyBzcGFjZSBvZiBJUHY2IGhh
cyBvZnRlbiBiZWVuDQo+ID4gPiA+IHBvcnRyYXllZCBhcyBhbGxvd2luZyBldmVyeXRoaW5nIGFy
b3VuZCB1cyB0byBoYXZlIGl0cyBvd24gSVANCj4gPiA+ID4gYWRkcmVzcy4gIEluIHRoZSBjb250
ZXh0IG9mIHZpcnR1YWwgd29ybGRzLCB0aGlzIGlkZWEgY2FuIGFjdHVhbGx5DQo+ID4gPiA+IGJl
IHB1dCB0byBnb29kIHVzZSwgd2l0aCBlYWNoIHZpcnR1YWwgb2JqZWN0IGJlYXJpbmcgaXRzIG93
biBJUHY2DQo+ID4gPiA+IGFkZHJlc3MuICBPbmUgY2FuZGlkYXRlIGFwcGxpY2F0aW9uIGZvciB0
aGlzIGhhcyBhbHJlYWR5IGJlZW4NCj4gPiA+ID4gZGVzY3JpYmVkIGluIGVhcmxpZXIgZGlzY3Vz
c2lvbnMgLS0tIGZvciBleGFtcGxlLCBpbXBsZW1lbnRpbmcNCj4gPiA+ID4gdmlydHVhbCBvYmpl
Y3Qgc2ltdWxhdGlvbiBpbiB0d28gcGFydHMsIG9uZSBjbGllbnQtc2lkZSBhbmQgb25lDQo+ID4g
PiA+IHdvcmxkLXNpZGUsIHRoZSB0d28gcGFydHMgY29tbXVuaWNhdGluZyBkaXJlY3RseS4gIElQ
djYgYWRkcmVzc2luZw0KPiA+ID4gPiBvZiBvYmplY3RzIG1ha2VzIHRoaXMgcmVsYXRpdmVseSBl
YXN5IHRvIGFjaGlldmUgZWZmaWNpZW50bHksIHNvIA0KPiA+IGl0cw0KPiA+ID4gPiBpbXBsZW1l
bnRhdGlvbiBpbiBJUHY2LWJhc2VkIHdvcmxkcyBpcyBhbG1vc3QgaW5ldml0YWJsZSBiZWZvcmUN
Cj4gPiA+ID4gbG9uZy4gIFZXUkFQIHNob3VsZCBiZSByZWFkeSBmb3IgdGhpcy4NCj4gPiA+ID4g
ICAg4oCiIFRoZSBldmVudCBxdWV1ZSBpbiBjdXJyZW50IGltcGxlbWVudGF0aW9ucyBwcm92aWRl
cyBhbiANCj4gPiBpbmRpcmVjdA0KPiA+ID4gPiBhbmQgaGlnaGx5IGluZWZmaWNpZW50IHdheSBv
ZiBhY2hpZXZpbmcgd29ybGQtdG8tY2xpZW50DQo+ID4gPiA+IGNvbW11bmljYXRpb25zLiAgSVB2
NiBvZmZlcnMgb3Bwb3J0dW5pdGllcyBmb3IgZGlyZWN0IA0KPiA+IGNvbW11bmljYXRpb24NCj4g
PiA+ID4gdGhhdCBjYW4gbWFrZSB0aGUgZXZlbnQgcXVldWUgYXBwcm9hY2ggb2Jzb2xldGUsIHNv
IGl0J3Mgd29ydGgNCj4gPiA+ID4gZXhhbWluaW5nIElQdjYtb3JpZW50ZWQgYWx0ZXJuYXRpdmVz
Lg0KPiA+ID4gPiAgICDigKIgV2UgcmVjZW50bHkgZGlzY3Vzc2VkIGZlYXR1cmUgYW5kIHByb3Rv
Y29sIG5lZ290aWF0aW9uIHdpdGhpbg0KPiA+ID4gPiBWV1JBUC4gIElQdjYgcHJvdmlkZXMgbXVj
aCBvcHBvcnR1bml0eSBmb3IgbmV3IGZlYXR1cmVzIGFuZCANCj4gPiBwcm90b2NvbA0KPiA+ID4g
PiBwYXRod2F5cyB0byBiZSBuZWdvdGlhdGVkIGJldHdlZW4gZW5kcG9pbnRzLCBzbyBpdCBnaXZl
cyB1cyBhIHZlcnkNCj4gPiA+ID4gcmVhbCBhbmQgaW1taW5lbnQgc2V0IG9mIHVzZSBjYXNlcyBm
b3IgbmVnb3RpYXRpb24uDQo+ID4gPiA+DQo+ID4gPiA+IEl0IHdvdWxkIGFsc28gYmUgYSBmZWF0
aGVyIGluIFZXUkFQJ3MgY2FwIHRvIGJlIGNvbnNpZGVyZWQgYW4gDQo+ID4gIklQdjYtDQo+ID4g
PiA+IGNhcGFibGUgYXBwbGljYXRpb24gcHJvdG9jb2wiIGluIGEgc3Ryb25nZXIgc2Vuc2UgdGhh
biBqdXN0IHRvIGJlDQo+ID4gPiA+IGNhcnJpZWQgYnkgSVB2NiBuZXR3b3Jrcy4gIElQdjYgZG9l
cyBhZnRlciBhbGwgYnJpbmcgbmV3IGFiaWxpdGllcw0KPiA+ID4gPiB0byB0aGUgdGFibGUsIHN1
Y2ggYXMgdGhlIGh1Z2UgYWRkcmVzc2luZywgYW5kIGl0IHdvdWxkIGJlIGEgDQo+ID4gbWlzdGFr
ZQ0KPiA+ID4gPiB0byBpZ25vcmUgdGhlbS4NCj4gPiA+ID4NCj4gPiA+ID4NCj4gPiA+ID4gTW9y
Z2FpbmUuDQo+ID4gPiA+DQo+ID4gPiA+DQo+ID4gPiA+DQo+ID4gPiA+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gPiA+IHZ3cmFwIG1haWxpbmcg
bGlzdA0KPiA+ID4gPiB2d3JhcEBpZXRmLm9yZw0KPiA+ID4gPiBodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3Z3cmFwDQo+ID4gPg0KPiA+ID4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiA+IHZ3cmFwIG1haWxpbmcgbGlzdA0K
PiA+ID4gdndyYXBAaWV0Zi5vcmcNCj4gPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vdndyYXANCj4gPg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQo+ID4gdndyYXAgbWFpbGluZyBsaXN0DQo+ID4gdndyYXBAaWV0Zi5v
cmcNCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Z3cmFwDQo+ID4N
Cj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+
IHZ3cmFwIG1haWxpbmcgbGlzdA0KPiA+IHZ3cmFwQGlldGYub3JnDQo+ID4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92d3JhcA0KPiA+DQo+ID4gX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiB2d3JhcCBtYWlsaW5nIGxpc3QN
Cj4gPiB2d3JhcEBpZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vdndyYXANCj4gPg0KPiA+DQo+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4gPiB2d3JhcCBtYWlsaW5nIGxpc3QNCj4gPiB2d3JhcEBpZXRm
Lm9yZw0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXANCj4g
Pg0KPiA+DQo+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4gPiB2d3JhcCBtYWlsaW5nIGxpc3QNCj4gPiB2d3JhcEBpZXRmLm9yZw0KPiA+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXANCj4gDQo+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IHZ3cmFwIG1haWxpbmcgbGlz
dA0KPiB2d3JhcEBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL3Z3cmFwDQoNCg==
--=_alternative 005652F785257729_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPisxIG9uIGFsbCBjb3VudHMgaGVy
ZS48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlRoZSBj
dXJyZW50IHNlcnZpY2UgZXN0YWJsaXNobWVudCBwYXR0ZW5zDQpwcm9wb3NlZCBpbiBWV1JBUCBp
cyBub3Qgb25seSBJUFY0L0lQVjYgYWdub3N0aWMsIGl0IGxldmVyYWdlcyB0aGUgPC9mb250Pg0K
PGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj53ZWIgYW5kIGludGVybmV0IGluIGFu
IGV4dHJlbWVseSB0cmFkaXRpb25hbA0KZmFzaGlvbi4gTmFtZWQgc2VydmljZXMgYXJlIHJlcXVl
c3QgdmlhIGEgY2FwYWJpbGl0eSBuYW1lIGFuZCA8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZh
Y2U9InNhbnMtc2VyaWYiPnNlZWRjYXAsIGFuZCBhIFVSSSBpcyByZXR1cm5lZCwgd2l0aA0KcG9z
c2libGUgY29udGVudCBuZWdvdGlhdGlvbiBhcyB0byBkZXRhaWxzLjwvZm9udD4NCjxicj4NCjxi
cj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7VGhlIHdob2xlIHBvaW50IG9m
IHJldHVybmluZyBhDQpVUkkgaXMgdG8gaXNvbGF0ZSBWV1JBUCBmcm9tIHRyYW5zcG9ydC4gVGhh
dCBVUkkgY291bGQgYmluZCBvbnRvIGFuIEhUVFAoUykNClVSTCwgb250bzwvZm9udD4NCjxicj48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+YW4gWE1QUCAmbmJzcDtlbmRwb2ludCwgb250
byBhIFJUUCBzdHJlYW0sDQpvbnRvIFNJUC4uLiA8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6
ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlRoZSBtb3N0IGNvbW1vbiBwcm9maWxlIGZvciBzb21lIHRp
bWUsDQppcyBsaWtlbHkgdGhhdCBtb3N0IHNlcnZpY2VzIHdpbGwgYmUgb24gYm9yaW5nIFVSTHMg
d2l0aCBib3JpbmcgaHR0cC9odHRwcw0KZW5kcG9pbnRzLCB3aXRoIG5hbWVzPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj53aGljaCBiaW5kIG9udG8gYm9yaW5nIElQ
VjQgYWRkcmVzc2VzLA0KYnV0LCBpdCBzaG91bGQgYmUgdG90YWxseSB0cmFuc3BhcmVudCB0byB0
aGUgaGlnaGVyIGxldmVsIGNvZGUgd2hldGhlcg0KdGhlIDwvZm9udD4NCjxicj48Zm9udCBzaXpl
PTIgZmFjZT0ic2Fucy1zZXJpZiI+bmV0d29yayBzdGFjayBpcyBWNCBvciBWNiwgb3IgVENQL0lQ
DQphdCBhbGwuIElmIEkgaGFkIGEgdmFsaWQgVVJJIHdoaWNoIGJvdW5kIG9udG8gYSBTTkEgTFUg
Ni4yIGVuZHBvaW50LCAmbmJzcDthbmQ8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPm1hdGNoaW5nIHRyYW5zcG9ydCBzdGFja3MsIGl0IG91Z2h0DQp0byB3b3JrLiA8
L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPi0gRGF2aWQ8
L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPn4gWmhhIDwvZm9udD4N
Cjxicj4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPnZ3cmFwLWJvdW5jZXNAaWV0Zi5vcmcg
d3JvdGUgb24gMDUvMjAvMjAxMCAxMToxOTo0NA0KQU06PGJyPg0KPGJyPg0KJmd0OyBbaW1hZ2Ug
cmVtb3ZlZF0gPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj4mZ3Q7IDxicj4NCiZn
dDsgUmU6IFt2d3JhcF0gVldSQVAgYW5kIElQdjY8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQg
c2l6ZT0yPiZndDsgPGJyPg0KJmd0OyBSaWNoYXJkIEJhcm5lcyA8L2ZvbnQ+PC90dD4NCjxicj48
dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyB0bzo8L2ZvbnQ+PC90dD4NCjxicj48dHQ+
PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyBNb3JnYWluZTwvZm9udD48L3R0Pg0KPGJyPjx0
dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+DQomZ3Q7IDA1LzIwLzIwMTAgMTE6MjAgQU08L2ZvbnQ+
PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyBTZW50IGJ5OjwvZm9u
dD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+DQomZ3Q7IHZ3cmFwLWJvdW5j
ZXNAaWV0Zi5vcmc8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0K
Jmd0OyBDYzo8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0
OyB2d3JhcDwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+DQomZ3Q7
IEknbSBsb3NpbmcgaW50ZXJlc3QgaW4gdGhpcyBkZWJhdGUsIGFuZCBJIHRoaW5rIHdlJ3ZlIGFs
bCBzYWlkIG91cg0KJm5ic3A7PGJyPg0KJmd0OyBwaWVjZSwgc28gSSdsbCBqdXN0IGNsb3NlIHdp
dGggYSByZWZlcmVuY2UgdG8gdGhlIHZlbmVyYWJsZSBSRkMgMTk1OCwNCiZuYnNwOzxicj4NCiZn
dDsgJnF1b3Q7QXJjaGl0ZWN0dXJhbCBQcmluY2lwbGVzIG9mIHRoZSBJbnRlcm5ldCZxdW90Ozo8
YnI+DQomZ3Q7ICZxdW90Ozxicj4NCiZndDsgJm5ic3A7ICZuYnNwOyBJbiBnZW5lcmFsLCB1c2Vy
IGFwcGxpY2F0aW9ucyBzaG91bGQgdXNlIG5hbWVzIHJhdGhlcg0KdGhhbiAmbmJzcDs8YnI+DQom
Z3Q7IGFkZHJlc3Nlcy48YnI+DQomZ3Q7ICZxdW90Ozxicj4NCiZndDsgKHRha2VuIGZyb20gYSBu
aWNlIHByZXNlbnRhdGlvbiB0aGF0IERhdmUgVGhhbGVyIGdhdmUgb24gaG93ICZuYnNwOzxicj4N
CiZndDsgcGF0aG9sb2dpY2FsIElQIGFkZHJlc3NlcyBjYW4gYmU6KTxicj4NCiZndDsgJmx0Ozwv
Zm9udD48L3R0PjxhIGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvNzMvc2xp
ZGVzL3BsZW5hcnl3LTEucGRmIj48dHQ+PGZvbnQgc2l6ZT0yPmh0dHA6Ly93d3cuaWV0Zi5vcmcv
cHJvY2VlZGluZ3MvNzMvc2xpZGVzL3BsZW5hcnl3LTEucGRmPC9mb250PjwvdHQ+PC9hPjx0dD48
Zm9udCBzaXplPTI+Jmd0Ozxicj4NCiZndDsgPGJyPg0KJmd0OyBGZWVsIGZyZWUgdG8gdXNlIElQ
djYgYWRkcmVzc2VzIGluIHRoZSBhcHBsaWNhdGlvbiBsYXllciBpZiB5b3Ugd2FudCwNCiZuYnNw
Ozxicj4NCiZndDsgYnV0IGJlIGF3YXJlIHRoYXQgdGhlcmUgYmUgZHJhZ29ucy48YnI+DQomZ3Q7
IDxicj4NCiZndDsgLS1SaWNoYXJkPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgT24g
TWF5IDIwLCAyMDEwLCBhdCAxMDo0NiBBTSwgTW9yZ2FpbmUgd3JvdGU6PGJyPg0KJmd0OyA8YnI+
DQomZ3Q7ICZndDsgQWJzdHJhY3Rpbmcgb3ZlciBhZGRyZXNzZXMgaXMgZmluZSwgUmljaGFyZCwg
YnV0IGFmdGVyIHlvdSd2ZQ0KZGVhbHQgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHdpdGggdGhlIGFi
c3RyYWN0aW9ucyB5b3UgdHlwaWNhbGx5IGVuZCB1cCB3aXRoIGFkZHJlc3NlcywgYW5kDQombmJz
cDs8YnI+DQomZ3Q7ICZndDsgdGhhdCdzIHdoYXQgcHJvdG9jb2xzIHdvcmsgd2l0aCBmcm9tIHRo
ZW4gb24uPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IFRoZSB0ZXh0dWFsIGFic3RyYWN0
aW9ucyBhcmUgb25seSB0aGVyZSBmb3IgaHVtYW4gY29tZm9ydCwgZWFzZQ0Kb2YgJm5ic3A7PGJy
Pg0KJmd0OyAmZ3Q7IGNvbmZpZ3VyYXRpb24sIGFuZCBncmVhdCBmbGV4aWJpbGl0eSBvZiBpbmRp
cmVjdGlvbiwgYnV0ICZuYnNwOzxicj4NCiZndDsgJmd0OyBhYnN0cmFjdGlvbnMgYXJlIGp1c3Qg
bWVhbnMgdG8gYW4gZW5kLiAmbmJzcDtBZnRlciB0aGUgYWRkcmVzcw0KJm5ic3A7PGJyPg0KJmd0
OyAmZ3Q7IGFic3RyYWN0aW9ucyBhcmUgZGUtYWJzdHJhY3RlZCwgcHJvdG9jb2xzIHdvcmsgd2l0
aCB0aGUgbXVjaA0KbW9yZSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgZWZmaWNpZW50IGJpbmFyeSBy
ZXByZXNlbnRhdGlvbnMuICZuYnNwO1RoYXQncyBwcmFjdGljYWxseSB1bml2ZXJzYWwuPGJyPg0K
Jmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IEl0J3MgZWFzeSB0byBnaXZlIGEgcHJhY3RpY2FsIGV4
YW1wbGUgb2Ygc3VjaCBvcGVyYXRpb24uICZuYnNwO0Zvcg0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7
IGV4YW1wbGUsIGNvbnNpZGVyIGEgZGVzaWduIGluIHdoaWNoIGFsbCBWVyBvYmplY3RzIGhhdmUg
dHdvIHBhcnRzLA0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGFuIGluLXdvcmxkIG9iamVjdCAoSVdP
KSBhbmQgYW4gaW4tY2xpZW50IG9iamVjdCAoSUNPKSwgd2hlcmUNCnRoZSAmbmJzcDs8YnI+DQom
Z3Q7ICZndDsgSUNPIGlzIHJlcGxpY2F0ZWQgaW4gZWFjaCBjbGllbnQuICZuYnNwO0xldCBib3Ro
IHBhcnRzIGJlIGFjdGl2ZSwNCmllLiAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgYm90aCBzaWRlcyBj
YW4gYmUgZXZlbnQgZ2VuZXJhdG9ycy4gJm5ic3A7SXQncyBlYXN5IGZvciBJQ09zDQp0byBhZGRy
ZXNzICZuYnNwOzxicj4NCiZndDsgJmd0OyB1cGRhdGUgZXZlbnRzIHRvIHRoZWlyIElXTyBiZWNh
dXNlIHRoZXJlIGlzIG9ubHkgb25lIElXTywgYW5kDQphY2Nlc3MgJm5ic3A7PGJyPg0KJmd0OyAm
Z3Q7IGNvdWxkIGJlIG9wdGltaXplZCB0byBuZXR3b3JrIGxldmVsIGFmdGVyIHRoZSBkZS1hYnN0
cmFjdGlvbg0Kc3RlcCAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgZm9yIGVmZmljaWVuY3kuICZuYnNw
O0J1dCB3aGF0IGFib3V0IHVwZGF0ZXMgaW4gdGhlIHJldmVyc2UgZGlyZWN0aW9uLA0KJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IHdoaWNoIGlzIDE6Tj88YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZn
dDsgSW4gdGhlIHR5cGljYWwgSVB2NCBlbnZpcm9ubWVudCwgdGhlIHVzdWFsIGFwcHJvYWNoIHdv
dWxkIGJlDQphICZuYnNwOzxicj4NCiZndDsgJmd0OyBoZWF2aWx5IGluZGlyZWN0ZWQgb25lLCB3
aXRoIHVwZGF0ZXMgdHJhdmVsbGluZyB0aHJvdWdoIGxheWVyDQp1cG9uICZuYnNwOzxicj4NCiZn
dDsgJmd0OyBsYXllciBvZiBtaWRkbGV3YXJlIGJlZm9yZSByZWFjaGluZyB0aGVpciB0YXJnZXQg
SUNPLiAmbmJzcDtJbg0KYW4gSVB2NiAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgZW52aXJvbm1lbnQg
aW4gd2hpY2ggZWFjaCBJQ08gY2FuIGhhdmUgaXRzIG93biBJUHY2IGFkZHJlc3MsDQp0aGVyZSAm
bmJzcDs8YnI+DQomZ3Q7ICZndDsgbmVlZCBiZSBubyBtaWRkbGV3YXJlIGF0IGFsbCBiZXR3ZWVu
IHRoZSBob3N0IGtlcm5lbCBhbmQgdGhlDQp0YXJnZXQgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IG9i
amVjdC4gJm5ic3A7VGhlIHJlc3VsdGluZyBpbmNyZWFzZSBpbiBlZmZpY2llbmN5IGJ5IG9yZGVy
cw0Kb2YgbWFnbml0dWRlICZuYnNwOzxicj4NCiZndDsgJmd0OyBjYW4gaGF2ZSBtYWpvciByYW1p
ZmljYXRpb25zIG9uIHRoZSBvcGVyYXRpb24gb2YgeW91ciB3b3JsZCBhbmQNCm9mICZuYnNwOzxi
cj4NCiZndDsgJmd0OyB5b3VyIGNsaWVudHMuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7
IEFuZCB0aGUgY29zdCBvZiB0aGlzIG1hc3NpdmUgbGVhcCBpbiBlZmZpY2llbmN5PyAmbmJzcDtN
ZXJlbHkNCnRvIGluZm9ybSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgdGhlIElXTyBvZiB0aGUgSUNP
J3MgZHluYW1pYyBJUHY2IG5ldHdvcmsgYWRkcmVzcywgd2hpY2ggYm9yZGVycw0Kb24gJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IHRoZSB0cml2aWFsLjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0
OyBPbmUgb2YgbXkgbWFpbiBpbnRlcmVzdHMgaXMgVlcgc2NhbGFiaWxpdHksIGJvdGggb2Ygd29y
bGRzIGFuZA0Kb2YgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGNsaWVudHMsIGFuZCBzdWNoIGVmZmlj
aWVuY3kgZ2FpbnMgYXJlIHRydWx5IGltcG9ydGFudC4gJm5ic3A7U2NhbGluZw0KVlcgJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IGNvbXBsZXhpdHkgYW5kIHJlbmRlcmluZyBvZiBjcm93ZHMgb3Igb2Yg
aGlnaGx5IGRldGFpbGVkICZuYnNwOzxicj4NCiZndDsgJmd0OyB2aXN1YWxpemF0aW9ucyByZXF1
aXJlcyBzb21lIGxhdGVyYWwgdGhpbmtpbmcgYW5kIG1vcmUgcG93ZXJmdWwNCiZuYnNwOzxicj4N
CiZndDsgJmd0OyBuZXR3b3JraW5nIHBhcmFkaWdtcyB0aGFuIHdlIGhhdmUgYmVlbiB1c2VkIHRv
IHVudGlsIG5vdy4gJm5ic3A7SVB2Ng0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IG9mZmVycyBzb21l
IGludGVyZXN0aW5nIHNvbHV0aW9ucyBpbiB0aGF0IGRpcmVjdGlvbiwgYW5kIHRoZXkNCndpbGwg
Jm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGJlIHVzZWQuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAm
Z3Q7PGJyPg0KJmd0OyAmZ3Q7IE1vcmdhaW5lLjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0
Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsg
Jmd0OyA9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PGJyPg0KJmd0OyAmZ3Q7PGJy
Pg0KJmd0OyAmZ3Q7IE9uIFRodSwgTWF5IDIwLCAyMDEwIGF0IDI6NDMgUE0sIFJpY2hhcmQgQmFy
bmVzICZsdDtyYmFybmVzQGJibi5jb20mZ3Q7DQombmJzcDs8YnI+DQomZ3Q7ICZndDsgd3JvdGU6
PGJyPg0KJmd0OyAmZ3Q7IEFzIGFuIGFzaWRlLCB0aGVyZSdzIG5vdGhpbmcgdGhhdCBzYXlzIHRo
YXQgc3Vic2NyaWJlcnMgaGF2ZQ0KdG8gYmUgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGFsbG9jYXRl
ZCBhIC82NC4gJm5ic3A7U29tZSBwcm9wb3NlZCBhZGRyZXNzaW5nIHNjaGVtZXMgdGhhdA0KYXJl
IG1vcmUgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGNvbnNlcnZhdGl2ZSAoaW4gdGhlIEFzaWEvUGFj
aWZpYyByZWdpb24gSUlSQykgYWN0dWFsbHkgYXNzaWduDQptdWNoICZuYnNwOzxicj4NCiZndDsg
Jmd0OyBsb25nZXIgcHJlZml4ZXMgKHNtYWxsZXIgYWRkcmVzcyBibG9ja3MpIHRvIGN1c3RvbWVy
cy48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgRmluZS1ncmFpbmVkIGFkZHJlc3NhYmls
aXR5IGlzIG5vdCB0aGUgc2FtZSBhcyBmaW5lLWdyYWluZWQgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7
IGFsbG9jYXRpb24gb2YgKklQKiBhZGRyZXNzZXMuIFRoaW5rIG9mIGl0IHRoaXMgd2F5OiBIVFRQ
IGhhcw0KdmVyeSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgZmluZS1ncmFpbmVkIGFkZHJlc3NhYmls
aXR5LCB3aXRoIGluZGl2aWR1YWwgaWRlbnRpZmllci9sb2NhdG9ycw0KZm9yICZuYnNwOzxicj4N
CiZndDsgJmd0OyBwYWdlcywgaW1hZ2VzLCBzY3JpcHRzLCBldGMuICZuYnNwO0l0J3MgYWJsZSB0
byBhY2NvbXBsaXNoIHRoaXMNCm5vdCBieSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgYXNzaWduaW5n
IGFuIElQdjYgYWRkcmVzcyB0byBldmVyeSBvYmplY3QsIGJ1dCBieSB1c2luZyBhbiAmbmJzcDs8
YnI+DQomZ3Q7ICZndDsgYXBwbGljYXRpb24tbGF5ZXIgaWRlbnRpZmllci9sb2NhdG9yIC0tIG5h
bWVseSBhIFVSTC48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgTm90IHVzaW5nIElQdjYg
YWRkcmVzc2VzIGluIGFwcGxpY2F0aW9ucyBpcyBub3QgcGFpbnRpbmcgb25lc2VsZg0KJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IGludG8gYW4gSVB2NCBjb3JuZXIsIGl0J3MgZ29vZCBwcm90b2NvbCBk
ZXNpZ24gZm9sbG93aW5nIHRoZQ0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGxheWVyaW5nIG1vZGVs
IG9mIHRoZSBJbnRlcm5ldC4gJm5ic3A7KElmIHdlJ3JlIHVzaW5nIElQdjQgYWRkcmVzc2VzDQpm
b3IgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGlkZW50aWZpZXJzLCB3ZSBzaG91bGRuJ3QgYmUgZG9p
bmcgdGhhdCBlaXRoZXIhKSAmbmJzcDtBYnN0cmFjdGluZw0Kb3ZlciAmbmJzcDs8YnI+DQomZ3Q7
ICZndDsgSVAgYWRkcmVzc2VzIGlzIGFib3V0IGZyZWVpbmcgdGhlIGFwcGxpY2F0aW9uIGZyb20g
aGF2aW5nIHRvDQp3b3JyeSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgYWJvdXQgd2hldGhlciBpdHMg
SVB2NCBvciBJUHY2IG9yIElQdjEwIG9yIFguMjUgb3Igd2hhdGV2ZXIgZWxzZQ0KYXQgJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IHRoZSBuZXR3b3JrIGxheWVyLjxicj4NCiZndDsgJmd0Ozxicj4NCiZn
dDsgJmd0OyAtLVJpY2hhcmQ8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7
ICZndDs8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgT24gTWF5IDIwLCAyMDEwLCBhdCA5
OjIzIEFNLCBNb3JnYWluZSB3cm90ZTo8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgT24g
VGh1LCBNYXkgMjAsIDIwMTAgYXQgMTA6NTkgQU0sIEhhbiBTb250c2UgJm5ic3A7PGJyPg0KJmd0
OyAmZ3Q7ICZsdDtoYW4uc29udHNlLnNsQGdtYWlsLmNvbSZndDsgd3JvdGU6PGJyPg0KJmd0OyAm
Z3Q7IEkgcmVjb2duaXplIHRoYXQgaXQgaXMgdGVtcGluZyB0byB0YWtlIGFkdmFudGFnZSBvZiB0
aGUgaHVnZQ0KYWRkcmVzcyAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgc3BhY2UgdGhhdCBJUHY2IG9m
ZmVycyBidXQgbXkgdGVzdCBlbmdpbmVlciBpbnN0aW5jdHMgdGVsbCBtZQ0KaXQgaXMgJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IHVud2lzZSB0byBkbyBzby48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7
ICZndDs8YnI+DQomZ3Q7ICZndDsgSSB0b28gYW0gYW4gZW5naW5lZXIsIGJ1dCBzb2xpZCBlbmdp
bmVlcmluZyBpbnN0aW5jdHMgZG8gbm90DQp0ZWxsIHVzICZuYnNwOzxicj4NCiZndDsgJmd0OyB0
byB1c2Ugb25seSB0aG9zZSBmYWNpbGl0aWVzIHdob3NlIG51bWJlcnMgb3Igc2l6ZXMgY2FuIGJl
IHRlc3RlZA0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGV4aGF1c3RpdmVseS4gJm5ic3A7SWYgaXQg
d2VyZSBzbywgd2Ugd291bGQgbm90IGhhdmUgbXVsdGktdGVyYWJ5dGUNCmRpc2sgJm5ic3A7PGJy
Pg0KJmd0OyAmZ3Q7IGRyaXZlcyB0b2RheS48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsg
VGhlIC82NCBtaW5pbXVtIHJvdXRhYmxlIHN1Ym5ldCBvZiBJUHY2IGFkZHJlc3Mgc3BhY2Ugd2Fz
IG5vdA0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGRlc2lnbmVkIGFzIGl0IHdhcyBiZWNhdXNlIHBl
b3BsZSB3ZXJlIGV4cGVjdGVkIHRvIG5lZWQgMl42NA0KTklDICZuYnNwOzxicj4NCiZndDsgJmd0
OyBjYXJkcyBpbiB0aGVpciBQQ3MuICZuYnNwO1RoaXMgaW1tZW5zZSBwZXItdXNlciBhZGRyZXNz
IGJsb2NrDQp3YXMgY3JlYXRlZCAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgYmVjYXVzZSBJUHY2IGRl
c2lnbmVycyBjb3VsZCBzZWUgYmV5b25kIElQdjQncyB1c2Ugb2YgYWRkcmVzc2VzDQpmb3IgJm5i
c3A7PGJyPg0KJmd0OyAmZ3Q7IGhvc3QgaW50ZXJmYWNlIGlkZW50aWZpY2F0aW9uLCBhbmQgd2Vy
ZSB2aXNpb25hcnkgZW5vdWdoIHRvIHJlYWxpemUNCiZuYnNwOzxicj4NCiZndDsgJmd0OyB0aGF0
IGFsbCBvYmplY3RzIGNvdWxkIGJlbmVmaXQgZnJvbSBuZXR3b3JrIGFkZHJlc3NhYmlsaXR5LiAm
bmJzcDtUaGlzDQombmJzcDs8YnI+DQomZ3Q7ICZndDsgYWxzbyBoYXBwZW5zIHRvIGJlIG9uZSBv
ZiB0aGUga2V5IG1lc3NhZ2VzIG9mIFJFU1QuICZuYnNwO0FkZHJlc3NhYmlsaXR5DQombmJzcDs8
YnI+DQomZ3Q7ICZndDsgaXMgZXh0cmVtZWx5IGltcG9ydGFudCwgdGhlIGZpbmVyIHRoZSBiZXR0
ZXIsIG5vdCBvbmx5IG9uIHRoZQ0KV2ViLCAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgYW5kIG5vdCBv
bmx5IHdpdGggVVJJcy48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgV2l0aCBJUHY2IGp1
c3QgYXJvdW5kIHRoZSBjb3JuZXIsIEkgZm9yZXNlZSBzdWNoIGFkZHJlc3NhYmlsaXR5DQphdCAm
bmJzcDs8YnI+DQomZ3Q7ICZndDsgZmluZSBsZXZlbHMgb2YgZ3JhbnVsYXJpdHkgYXBwZWFyaW5n
IGluIFZXcyByZWxhdGl2ZWx5IHNvb24uDQombmJzcDtJUHY0ICZuYnNwOzxicj4NCiZndDsgJmd0
OyB3b3JsZHMgd2lsbCBoYXZlIHRvIGVtdWxhdGUgd2hhdCBJUHY2IHdvcmxkcyBhY2hpZXZlIG5h
dGl2ZWx5LA0KYW5kICZuYnNwOzxicj4NCiZndDsgJmd0OyB0aGF0IGlzIHRoZSByaWdodCB3YXkg
YXJvdW5kLiAmbmJzcDtXaGVuIGxlZ2FjeSBkZXNpZ24gcmVzdHJpY3RzDQombmJzcDs8YnI+DQom
Z3Q7ICZndDsgcHJvZ3Jlc3MsIHRoZSBvbmx5IHRoaW5nIGl0IGFjaGlldmVzIGlzIHJhcGlkIG9i
c29sZXNjZW5jZS48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgSSB3b3VsZCBwcmVmZXIg
VldSQVAgbm90IHRvIGJlIHBhaW50aW5nIGl0c2VsZiBpbnRvIGFuIElQdjQgY29ybmVyDQombmJz
cDs8YnI+DQomZ3Q7ICZndDsgb2Ygb2Jzb2xlc2NlbmNlIGJlZm9yZSBpdCdzIGV2ZW4gcmVsZWFz
ZWQsIHdoaWNoIGlzIHdoeSBJJ20gcmFpc2luZw0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHRoaXMg
dG9waWMgLS0tIGl0J3MgaW50ZW5kZWQgYXMgYSBoZWFkcy11cCBmb3IgdGhlIGdyb3VwLjxicj4N
CiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBTaW5jZSB0aGUgcmlzZSBvZiBWV3MgYW5kIElQdjYg
dGFrZS11cCBhcmUgZ29pbmcgdG8gb2NjdXIgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGNvbmN1cnJl
bnRseSwgSSB0aGluayB0aGUgbmV4dCBmZXcgeWVhcnMgYXJlIGdvaW5nIHRvIGJlIHZlcnkNCiZu
YnNwOzxicj4NCiZndDsgJmd0OyBpbnRlcmVzdGluZyBvbiB0aGUgVlcgbmV0d29ya2luZyBmcm9u
dC4gJm5ic3A7TXkgcmVjb21tZW5kYXRpb24NCmlzIHRvICZuYnNwOzxicj4NCiZndDsgJmd0OyBv
YnNlcnZlIGNhcmVmdWxseSB3aGF0IGhhcHBlbnMsIGFuZCBub3QgdG8gbWFrZSBhbnkgcmFzaCBk
ZWNpc2lvbnMNCiZuYnNwOzxicj4NCiZndDsgJmd0OyBiYXNlZCBvbiBsZWdhY3kgaWRlYXMgdGhh
dCBjb3VsZCBjdXQgb2ZmIHlvdXIgZnV0dXJlLjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0
Ozxicj4NCiZndDsgJmd0OyBNb3JnYWluZS48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDs8
YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZn
dDsgPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT08YnI+DQomZ3Q7ICZndDs8YnI+
DQomZ3Q7ICZndDsgT24gVGh1LCBNYXkgMjAsIDIwMTAgYXQgMTA6NTkgQU0sIEhhbiBTb250c2Ug
Jm5ic3A7PGJyPg0KJmd0OyAmZ3Q7ICZsdDtoYW4uc29udHNlLnNsQGdtYWlsLmNvbSZndDsgd3Jv
dGU6PGJyPg0KJmd0OyAmZ3Q7IEl0J3MgYSBiYWQgaWRlYSB0byB1c2UgSVAgYWRkcmVzc2VzIGZv
ciBhbnl0aGluZyBvdGhlciB0aGFuICZuYnNwOzxicj4NCiZndDsgJmd0OyBhZGRyZXNzaW5nIGEg
bWFjaGluZSBsZXZlbCBpbnRlcmZhY2UuICZuYnNwO1VzaW5nIHRoZW0gdG8gaW50ZXJmYWNlDQom
bmJzcDs8YnI+DQomZ3Q7ICZndDsgb2JqZWN0cyBhdCBvciBhYm92ZSB0aGUgYXBwbGljYXRpb24g
bGV2ZWwgaXMgYXNraW5nIGZvciB0cm91YmxlLg0KJm5ic3A7ICZuYnNwOzxicj4NCiZndDsgJmd0
OyBVVUlEcyBhcmUgVVVJRHMuLi4gSVAgYWRkcmVzc2VzIGFyZSBJUCBhZGRyZXNzZXMuICZuYnNw
OyBUaGUNCnR3byBzaG91bGQgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IG5vdCBiZSBtaXhlZC4gJm5i
c3A7IEkgcmVjb2duaXplIHRoYXQgaXQgaXMgdGVtcGluZyB0byB0YWtlIGFkdmFudGFnZQ0Kb2Yg
Jm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHRoZSBodWdlIGFkZHJlc3Mgc3BhY2UgdGhhdCBJUHY2IG9m
ZmVycyBidXQgbXkgdGVzdCBlbmdpbmVlcg0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGluc3RpbmN0
cyB0ZWxsIG1lIGl0IGlzIHVud2lzZSB0byBkbyBzby48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7
ICZndDsgSGFuLjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBPbiBNYXkgMjAsIDIwMTAs
IGF0IDI6NTAgQU0sIE1vcmdhaW5lIHdyb3RlOjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0
OyBBIC82NCBpcyB0aGUgc21hbGxlc3Qgcm91dGFibGUgSVB2NiBzdWJuZXQsIGhlbmNlIHRoZXJl
IGlzIG5vDQpleHRyYSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgcm91dGluZyBvdmVyaGVhZCBmb3Ig
dGhlIDJeKDEyOC02NCkgYWRkcmVzc2VzIGluIHRoZSBiYXNpYyBibG9jaw0KJm5ic3A7PGJyPg0K
Jmd0OyAmZ3Q7IHRoYXQgZXZlcnkgdXNlciB3aWxsIGhhdmUgYWxsb2NhdGVkLjxicj4NCiZndDsg
Jmd0Ozxicj4NCiZndDsgJmd0OyBOZWVkbGVzcyB0byBzYXksIHRoZXJlIHdvbid0IGJlIGFueXRo
aW5nIGxpa2UgMl42NCBvYmplY3RzIGluDQp5b3VyICZuYnNwOzxicj4NCiZndDsgJmd0OyBzY2Vu
ZWdyYXBoLCBzbyBpZiB5b3UgdXNlIHlvdXIgSVB2NiBhZGRyZXNzIHNwYWNlIHRvIGFkZHJlc3MN
CmV2ZXJ5ICZuYnNwOzxicj4NCiZndDsgJmd0OyBzY2VuZWdyYXBoIG9iamVjdCB0aGF0IHlvdSBo
YXZlIGluc3RhbnRpYXRlZCBjbGllbnQtc2lkZSwgeW91DQp3aWxsICZuYnNwOzxicj4NCiZndDsg
Jmd0OyBzdGlsbCBoYXZlIGFuIGV4dHJlbWVseSBzcGFyc2VseSB1c2VkIC82NCBibG9jay4gJm5i
c3A7WW91J2xsDQpiZSBrZWVwaW5nICZuYnNwOzxicj4NCiZndDsgJmd0OyB0cmFjayBvZiB3aGlj
aCBhZGRyZXNzZXMgeW91IGhhdmUgYXNzaWduZWQgZHluYW1pY2FsbHkgb2YgY291cnNlLg0KJm5i
c3A7PGJyPg0KJmd0OyAmZ3Q7IChBbiBhZGRyZXNzIHNwYWNlIG9mIHRoaXMgc2l6ZSBpcyBub3Qg
bGluZWFybHkgc2Nhbm5hYmxlIGluICZuYnNwOzxicj4NCiZndDsgJmd0OyByZWFsaXN0aWMgdGlt
ZS4pPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IEluIHByaW5jaXBsZSB0aGlzIGlzIG5v
IGRpZmZlcmVudCB0byB1c2luZyBVVUlEcyAtLS0geW91ciBJUHY2DQptaWNyby0gPGJyPg0KJmd0
OyAmZ3Q7IHNlcnZlcnMgd2lsbCBoYXZlIHVuZ3Vlc3NhYmxlIElQdjYgYWRkcmVzc2VzIHdpdGhp
biB5b3VyIC82NA0KYmxvY2ssICZuYnNwOzxicj4NCiZndDsgJmd0OyBhbmQgaXQnbGwgYmUgdXAg
dG8geW91IHRvIHRlbGwgb3RoZXIgcGFydGljaXBhbnRzIGluIHRoZSBwcm90b2NvbA0KJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IChmb3IgZXhhbXBsZSBzZXJ2ZXItc2lkZSBvYmplY3RzKSB3aXRoIHdo
aWNoIG9mIHlvdXIgSVB2NiBtaWNyby0NCjxicj4NCiZndDsgJmd0OyBzZXJ2ZXJzIHRoZXkgYXJl
IHRvIGNvbW11bmljYXRlLiAmbmJzcDtUaGlzIGlzIHdoeSBhbiBBRFQgdGhhdA0KaXMgJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IHN1cHBvcnRpdmUgb2YgSVB2NiBvcGVyYXRpb24gbmVlZHMgdG8gYmUg
YWJsZSB0byBjYXJyeSBzdWNoIGRhdGENCiZuYnNwOzxicj4NCiZndDsgJmd0OyBlZmZpY2llbnRs
eSAtLS0gdGhlIFVVSUQgaXMgbm8gbG9uZ2VyIHRoZSBvbmx5IDEyOC1iaXQgZGF0dW0NCm9mICZu
YnNwOzxicj4NCiZndDsgJmd0OyBpbnRlcmVzdC48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZn
dDsgT2YgY291cnNlIHlvdXIgZW50aXJlIC82NCBibG9jayBpcyByb3V0ZWQgYXMgb25lLCBzaW5j
ZSB0aGVyZQ0KYXJlIG5vICZuYnNwOzxicj4NCiZndDsgJmd0OyBzbWFsbGVyIHJvdXRhYmxlIHN1
Ym5ldHMgaW4gSVB2NiwgYW5kIHRoZXJlZm9yZSB5b3VyIG9iamVjdGlvbnMNCiZuYnNwOzxicj4N
CiZndDsgJmd0OyBhYm91dCByb3V0aW5nIG5vbi1zY2FsYWJpbGl0eSBkbyBub3QgYXBwbHkuPGJy
Pg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IE1vcmdhaW5lLjxicj4N
CiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxi
cj4NCiZndDsgJmd0OyA9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PGJyPg0K
Jmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IE9uIFdlZCwgTWF5IDE5LCAyMDEwIGF0IDEwOjU2IFBN
LCBSaWNoYXJkIEJhcm5lcyAmbHQ7cmJhcm5lc0BiYm4uY29tJmd0Ow0KJm5ic3A7PGJyPg0KJmd0
OyAmZ3Q7IHdyb3RlOjxicj4NCiZndDsgJmd0OyBUaGUgaW1wYWN0IG9mIElQdjYgb24gVldzIHNo
b3VsZCBiZSBmYXIgbGVzcyB0aGFuIHlvdSBpbWFnaW5lLA0KSSAmbmJzcDs8YnI+DQomZ3Q7ICZn
dDsgdGhpbmsuIDopPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IEl0IGhhcyBvZnRlbiBi
ZWVuIHNhaWQgdGhhdCBtYW55LCBtYW55IHRoaW5ncyB3aWxsIGJlIGFzc2lnbmVkDQpJUHY2ICZu
YnNwOzxicj4NCiZndDsgJmd0OyBhZGRyZXNzZXMuICZuYnNwO1RoZXJlIHdpbGwgY2VydGFpbmx5
IGJlIGVub3VnaCB0byBnbyBhcm91bmQsDQpidXQgdGhhdCAmbmJzcDs8YnI+DQomZ3Q7ICZndDsg
ZG9lc24ndCBtYWtlIHRoZW0gZ29vZCBhcHBsaWNhdGlvbi1sYXllciBpZGVudGlmaWVycy4gJm5i
c3A7SWYNCnlvdSB3YW50ICZuYnNwOzxicj4NCiZndDsgJmd0OyB0byB1c2UgSVAgYWRkcmVzc2Vz
IHdpdGggSVAsIHRoZXkgaGF2ZSB0byByb3V0ZSwgYW5kIHRoYXQgbWVhbnMNCnRoYXQgJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IHRoZXkgaGF2ZSB0byBiZSBlaXRoZXIgKDEpIHRvcG9sb2dpY2FsbHkg
YXNzaWduZWQsIG9yICgyKSBvdmVybGF5DQombmJzcDs8YnI+DQomZ3Q7ICZndDsgcm91dGVkLCBl
LmcuLCB3aXRoIG1vYmlsZSBJUC4gJm5ic3A7U28gaWYgeW91IHdhbnQgdG8gdXNlIGFuDQpJUCBh
ZGRyZXNzICZuYnNwOzxicj4NCiZndDsgJmd0OyB0byBhZGRyZXNzIHNvbWV0aGluZywgeW91J3Jl
IGdvaW5nIHRvIGhhdmUgdG8gZWl0aGVyIGNoYW5nZSB0aGF0DQombmJzcDs8YnI+DQomZ3Q7ICZn
dDsgYWRkcmVzcyB3aGVuIHRoZSB0aGluZyBnZXRzIGNvbm5lY3RlZCBkaWZmZXJlbnRseSwgb3Ig
eW91J2xsDQpuZWVkICZuYnNwOzxicj4NCiZndDsgJmd0OyBzb21lIG92ZXJsYXkgcm91dGluZyBz
Y2hlbWUgdG8gcm91dGUgdG8gYSBwZXJzaXN0ZW50IGFkZHJlc3MuDQombmJzcDsoQW5kICZuYnNw
Ozxicj4NCiZndDsgJmd0OyBpZiB5b3UncmUgbm90IGdvaW5nIHRvIHVzZSB0aGUgYWRkcmVzcyB3
aXRoIElQLCB0aGVuIHdoeSB3b3VsZA0KeW91ICZuYnNwOzxicj4NCiZndDsgJmd0OyB1c2UgYW4g
SVAgYWRkcmVzcz8pPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IFZXUkFQLCBhcyBhbiBh
cHBsaWNhdGlvbiBsYXllciBwcm90b2NvbCwgaGFzIGEgY2hvaWNlIGFib3V0IHdoYXQNCiZuYnNw
Ozxicj4NCiZndDsgJmd0OyBpZGVudGlmaWVycyB0byB1c2UgZm9yIHRoaW5ncyBhbmQgaG93IHRv
IHVzZSB0aG9zZSBpZGVudGlmaWVycy4NCiZuYnNwOyA8YnI+DQomZ3Q7ICZndDsgSVNUTSB0aGF0
IHVzaW5nIElQIGFkZHJlc3NlcyAoYWdhaW4sIG9mIGVpdGhlciB0eXBlKSByZW1haW5zDQphIGJh
ZCAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgaWRlYSwgY29tcGFyZWQgd2l0aCBzb21ldGhpbmcgdGhh
dCBpcyBkZWNvdXBsZWQgZnJvbSB0aGUgcm91dGluZw0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGxh
eWVyLjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBBcyBmYXIgYXMgdGhlIEROUywgSSdt
IG5vdCBzdXJlIHdoYXQgeW91ciBwb2ludCBpczo8YnI+DQomZ3Q7ICZndDsgKGkpIEROUyBjYWNo
aW5nIGhhcyBiZWVuIGFyb3VuZCBmb3IgZGVjYWRlczxicj4NCiZndDsgJmd0OyAoaWkpIEROUyBu
YW1lcyBjYW4gYWxyZWFkeSByZWZlciB0byBtdWx0aXBsZSBhZGRyZXNzZXM8YnI+DQomZ3Q7ICZn
dDsgKGlpaSkgRGVwZW5kcyBvbiBpbXBsZW1lbnRhdGlvbi4gJm5ic3A7TWF5YmUgdGhlcmUncyBz
b21lIGFwcGxpY2F0aW9uLQ0KPGJyPg0KJmd0OyAmZ3Q7IGxheWVyIHdheSB0byByZXNvbHZlIG5h
bWVzLiAmbmJzcDtFLmcuLCBTSVAgZW5kcG9pbnRzIGRvbid0IG5lZWQNCnRvIGhhdmUgJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IEROUyByZWNvcmRzIGJlY2F1c2UgdGhlIElOVklURSB0cmFuc2FjdGlv
biBtYXBzIGZyb20gU0lQIFVSSXMNCnRvIElQICZuYnNwOzxicj4NCiZndDsgJmd0OyBhZGRyZXNz
ZXMuPGJyPg0KJmd0OyAmZ3Q7IChpdikgRnJvbSBSRkMgNDI5MTogJnF1b3Q7SVB2NiBhZGRyZXNz
ZXMgYXJlIDEyOC1iaXQgaWRlbnRpZmllcnMNCmZvciAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgaW50
ZXJmYWNlcyBhbmQgc2V0cyBvZjxicj4NCiZndDsgJmd0OyBpbnRlcmZhY2VzJnF1b3Q7PGJyPg0K
Jmd0OyAmZ3Q7ICh2KSBTZWVtcyBsaWtlIHRoZXJlJ3MgYSB1c2UgY2FzZSBsdXJraW5nLCBoYXJk
IHRvIGFkZHJlc3Mgd2l0aG91dA0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGRldGFpbHMuICZuYnNw
O0J1dCB5b3UncmUgcHJvYmFibHkgc3RpbGwgYXQgdGhlIGFwcGxpY2F0aW9uIGxheWVyLg0KJm5i
c3A7Rm9yICZuYnNwOzxicj4NCiZndDsgJmd0OyBpbnN0YW5jZSwgaWYgeW91IHdlcmUgdGVsbGlu
ZyB5b3VyIHBlZXIgdG8gc2VuZCB5b3UgYW4gSFRUUCByZXF1ZXN0LA0KJm5ic3A7PGJyPg0KJmd0
OyAmZ3Q7IHlvdSB3b3VsZCBzZW5kIGFuIEhUVFAgVVJJLCB3aGljaCBjYW4gYWxyZWFkeSBoYW5k
bGUgSVB2NiBhZGRyZXNzZXMuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IC0tUmljaGFy
ZDxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsg
Jmd0OyBPbiBNYXkgMTksIDIwMTAsIGF0IDk6MzUgQU0sIE1vcmdhaW5lIHdyb3RlOjxicj4NCiZn
dDsgJmd0Ozxicj4NCiZndDsgJmd0OyBUaGUgaW1wYWN0IG9mIElQdjYgb24gVldzIGlzIGdvaW5n
IHRvIGJlIGZhciBncmVhdGVyIHRoYW4geW91DQombmJzcDs8YnI+DQomZ3Q7ICZndDsgaW1hZ2lu
ZSwgSSBiZWxpZXZlLiAmbmJzcDtBcyB0aGluZ3Mgc3RhbmQsIFZXUkFQIGlzIGJlaW5nIGRlc2ln
bmVkDQphcm91bmQgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHRoZSBmZWF0dXJlcyBhbmQgbGltaXRh
dGlvbnMgb2YgSVB2NCBuZXR3b3JraW5nLiAmbmJzcDtJdCB3aWxsDQpvZiBjb3Vyc2UgJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IGJlIGFibGUgdG8gcmlkZSBvbiB0b3Agb2YgSVB2NiBhcyBhIHRyYW5z
cG9ydCwgYnV0IHVuYWJsZSB0bw0KYmVuZWZpdCAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgZnJvbSBp
dHMgaW1wcm92ZWQgZmVhdHVyZSBzZXQsIHVubGVzcyB3ZSBwcm92aWRlIHRoZSBtZWFucyB0bw0K
ZG8gc28uPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IFRoZSBxdWVzdGlvbiAmcXVvdDtX
aHkgaXMgdGhlcmUgZXZlciBhIG5lZWQgdG8gY2FycnkgYW4gSVAgYWRkcmVzcw0KaW4gJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IHRoaXMgYXBwbGljYXRpb24tbGF5ZXIgcHJvdG9jb2wsIGFzIG9wcG9z
ZWQgdG8sIHNheSwgYSBETlMgbmFtZQ0Kb3IgYSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgVVJJPyZx
dW90OyBzdWdnZXN0cyBhbiBJUHY0IG1pbmRzZXQsIGJlY2F1c2UgaW4gSVB2NiBpdCBoYXMgYQ0K
dmFyaWV0eSBvZiAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgcG9zc2libGUgYW5zd2VyczogJm5ic3A7
KGkpIFdoZW4gdGhlIEROUyBsb29rdXAgaGFzIGFscmVhZHkgYmVlbg0KZG9uZSBhbmQgJm5ic3A7
PGJyPg0KJmd0OyAmZ3Q7IGRvZXMgbm90IG5lZWQgdG8gYmUgZG9uZSBhZ2FpbiwgKGlpKSBXaGVu
IGEgRlFETiBtYXBzIHRvIG11bHRpcGxlDQombmJzcDs8YnI+DQomZ3Q7ICZndDsgYWRkcmVzc2Vz
LCBidXQgeW91IHdhbnQgdG8gcmVmZXIgdG8gYSBzcGVjaWZpYyBvbmUsIChpaWkpIFdoZW4NCmFu
ICZuYnNwOzxicj4NCiZndDsgJmd0OyBJUHY2IGFkZHJlc3MgZG9lcyBub3QgaGF2ZSBhbiBleHRl
cm5hbCBhZGRyZXNzIHJlY29yZCwgKGl2KSBXaGVuDQp0aGUgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7
IGhvc3QgaXMgYWxyZWFkeSBrbm93biBhbmQgdGhlIElQIGFkZHJlc3MgZGVub3RlcyBzb21ldGhp
bmcgb3RoZXINCiZuYnNwOzxicj4NCiZndDsgJmd0OyB0aGFuIGEgcGh5c2ljYWwgTklDIGludGVy
ZmFjZSwgb3IgKHYpIFdoZW4gbGlzdGVuZXJzIGFyZSBhbGxvY2F0ZWQNCiZuYnNwOzxicj4NCiZn
dDsgJmd0OyBsb2NhbGx5IGFuZCBkeW5hbWljYWxseSBmb3IgdGhlIGN1cnJlbnQgc2Vzc2lvbiBv
bmx5LCBhbmQgdGhlaXINCklQICZuYnNwOzxicj4NCiZndDsgJmd0OyBhZGRyZXNzZXMgbmVlZCB0
byBiZSBjb21tdW5pY2F0ZWQgdG8gYSBwZWVyIC0tLSB0aGlzIHdpbGwgYmUNCmFuICZuYnNwOzxi
cj4NCiZndDsgJmd0OyBleHRyZW1lbHkgY29tbW9uIHVzZSBjYXNlIHdpdGggSVB2Ni48YnI+DQom
Z3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgSW4gdG9kYXkncyBJUHY0LWJhc2VkIHN5c3RlbXMsIGl0
IGlzIG5vcm1hbCBmb3IgYSB1c2VyJ3MgbWFjaGluZQ0KdG8gJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7
IGhhdmUgYSBzaW5nbGUgSVAgYWRkcmVzcywgYW5kIGZvciBhIGNsaWVudCBvbiB0aGF0IG1hY2hp
bmUgdG8NCnRhbGsgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHRvIGEgc2VydmVyIHRoYXQgaGFzIGEg
c2luZ2xlIGN1c3RvbWVyLWZhY2luZyBJUCBhZGRyZXNzIHRvbw0KJm5ic3A7PGJyPg0KJmd0OyAm
Z3Q7IChhbHRob3VnaCBpdCBtYXkgYWxzbyBoYXZlIG90aGVycyB0aGF0IGFyZSBub3QgcHVibGlj
KS4gJm5ic3A7SW4NCklQdjYtIDxicj4NCiZndDsgJmd0OyBiYXNlZCBzeXN0ZW1zLCB0aGlzIHNp
bXBsZSBzY2VuYXJpbyBpcyBzdGlsbCBwb3NzaWJsZSBidXQgcmVwcmVzZW50cw0KJm5ic3A7PGJy
Pg0KJmd0OyAmZ3Q7IG9ubHkgYSBzcGVjaWFsIGNhc2UgYW1vbmcgYSBuZXcgYW5kIHZhc3RseSBl
eHBhbmRlZCBzZXQgb2YgSVB2Ng0KdXNlICZuYnNwOzxicj4NCiZndDsgJmd0OyBjYXNlcy48YnI+
DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgVGhlIHNtYWxsZXN0IGFsbG9jYXRhYmxlIGJsb2Nr
IG9mIElQdjYgYWRkcmVzcyBzcGFjZSBpcyBhIC82NCwNCnNvICZuYnNwOzxicj4NCiZndDsgJmd0
OyAyXigxMjgtNjQpIElQIGFkZHJlc3NlcyBpcyB0aGUgbnVtYmVyIHRoYXQgbW9zdCBub3JtYWwg
SVB2NiB1c2Vycw0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHdpbGwgaGF2ZSwgYWx0aG91Z2ggdGhl
IG11Y2ggbGFyZ2VyIC80OCBibG9ja3Mgb2YgMl44MCBhZGRyZXNzZXMNCmFyZSAmbmJzcDs8YnI+
DQomZ3Q7ICZndDsgY29tbW9ubHkgYXNzaWduZWQgdG8gdXNlcnMgYXMgd2VsbC4gJm5ic3A7V2l0
aCBzdWNoIElQIHJpY2hlcw0KY2xpZW50LSA8YnI+DQomZ3Q7ICZndDsgc2lkZSwgaXQgaXMgY2Vy
dGFpbiB0aGF0IHRoZXkgd2lsbCBiZSB1c2VkIGZvciBzb21ldGhpbmcsIGFuZA0KdGhlICZuYnNw
Ozxicj4NCiZndDsgJmd0OyBvYnZpb3VzIHN1Z2dlc3Rpb24gaXMgdG8gZ2l2ZSBldmVyeSBWVyBv
YmplY3QgYW4gSVB2NiBhZGRyZXNzDQpvZiBpdHMgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IG93bi48
YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgTGVzdCB3ZSBmb3JnZXQsIG9uZSBvZiB0aGUg
bW9zdCBpbXBvcnRhbnQgcHJvcGVydGllcyBvZiB0aGUgUkVTVA0KJm5ic3A7PGJyPg0KJmd0OyAm
Z3Q7IHBhcmFkaWdtIGlzIGFkZHJlc3NhYmlsaXR5LCBidXQgdGhlIGJlbmVmaXRzIG9mIGhpZ2gg
YWRkcmVzc2FiaWxpdHkNCiZuYnNwOzxicj4NCiZndDsgJmd0OyBnbyBmYXIgYmV5b25kIHRoZSBX
ZWIuICZuYnNwO1RoaXMgaXMgYSBwcm9wZXJ0eSB0aGF0IHdpbGwgYmVjb21lDQombmJzcDs8YnI+
DQomZ3Q7ICZndDsgdWJpcXVpdG91cyB0aHJvdWdob3V0IG5ldHdvcmtlZCBjb21wdXRpbmcgd2l0
aCBJUHY2LiAmbmJzcDtJdCdzDQpwcm9iYWJseSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgbm8gZXhh
Z2dlcmF0aW9uIHRvIHNheSB0aGF0ICpldmVyeXRoaW5nKiB3aWxsIGJlIGdldHRpbmcgaXRzDQpv
d24gSVAgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGFkZHJlc3MuIDotKTxicj4NCiZndDsgJmd0Ozxi
cj4NCiZndDsgJmd0OyBGYWNlZCB3aXRoIHRoYXQgZnV0dXJlLCBpdCdzIGEgbWlzdGFrZSB0byB0
aGluayBpbiBJUHY0IHRlcm1zDQphbmQgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGNvbnNpZGVyIElQ
djYgYWRkcmVzc2VzIGFzIG1lcmVseSBkZW5vdGluZyBhIGhvc3Qgd2hpY2ggY2FuIGJlDQombmJz
cDs8YnI+DQomZ3Q7ICZndDsgb2J0YWluZWQgZnJvbSBpdHMgRlFETi4gJm5ic3A7VGhhdCdzIElQ
djQgdGhpbmtpbmcsIGFuZCByZXByZXNlbnRzDQpvbmx5IGEgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7
IHZlcnkgYmFzaWMgdXNlIGNhc2UgZm9yIElQdjYuICZuYnNwO0luIG1vcmUgZXh0ZW5kZWQgdXNl
IGNhc2VzLA0KSVB2NiAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgYWRkcmVzc2VzIHdpbGwgYmVjb21l
IG11Y2ggbW9yZSBsaWtlIGFjdGl2ZSBsb2NhbCBVVUlEcyB0aGFuDQpsaWtlICZuYnNwOzxicj4N
CiZndDsgJmd0OyB0b2RheSdzIGhvc3QgSVAgYWRkcmVzc2VzLiAmbmJzcDtUaGV5IHdpbGwgYmUg
dXNlZCBmb3IgaW5uZXItYXBwbGljYXRpb24NCiZuYnNwOzxicj4NCiZndDsgJmd0OyBhZGRyZXNz
aW5nLCBmb3IgZXhhbXBsZSB0byBtYWtlIGV2ZXJ5IG9iamVjdCBpbiBhbiBhcHBsaWNhdGlvbg0K
YW4gJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGFkZHJlc3NhYmxlIG1pY3JvLXNlcnZlci48YnI+DQom
Z3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgVldSQVAgaXMgYmVpbmcgYm9ybiBpbnRvIGFuIElQdjYg
d29ybGQsIGFuZCBpdCB3b3VsZCBiZSBhIG1pc3Rha2UNCnRvICZuYnNwOzxicj4NCiZndDsgJmd0
OyBoYXJkd2lyZSBJUHY0IHRoaW5raW5nIGludG8gaXRzIGRlc2lnbi4gJm5ic3A7V2UgY29udGlu
dWFsbHkNCnJlZmVyIHRvIHRoZSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgbmVlZCBmb3IgZXh0ZW5z
aWJpbGl0eSBhbmQgYSBkZXNpcmUgdG8gZnV0dXJlLXByb29mIHRoZSBwcm90b2NvbCwNCiZuYnNw
Ozxicj4NCiZndDsgJmd0OyBidXQgbGlwIHNlcnZpY2UgaXMgbm90IGVub3VnaC4gJm5ic3A7QWRk
aW5nIElQdjYgYWRkcmVzc2VzIHRvDQp0aGUgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHVuZGVybHlp
bmcgQURUIHdvdWxkIHByb3ZpZGUgYSBiYXJlIG1pbmltdW0gbGV2ZWwgb2YgdGhpbmtpbmcNCmFo
ZWFkICZuYnNwOzxicj4NCiZndDsgJmd0OyB0byBzdXBwb3J0IFZXUkFQIGltcGxlbWVudGF0aW9u
cyB0aGF0IGVtYnJhY2UgbGFyZ2UgbnVtYmVycyBvZg0KJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGNv
bW11bmljYXRpbmcgb2JqZWN0cy4gJm5ic3A7KEEgZ2VuZXJhbGx5IGV4dGVuc2libGUgQURUIHdv
dWxkDQpvZiBjb3Vyc2UgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGFjaGlldmUgdGhlIHNhbWUgdGhp
bmcsIGFuZCBtb3JlLik8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZn
dDsgTW9yZ2FpbmUuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7
PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAm
Z3Q7PGJyPg0KJmd0OyAmZ3Q7ID09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT08YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgT24gTW9uLCBNYXkgMTcsIDIw
MTAgYXQgMzo1MCBQTSwgRGF2aWQgVyBMZXZpbmUgJmx0O2R3bEB1cy5pYm0uY29tJmd0Ow0KJm5i
c3A7PGJyPg0KJmd0OyAmZ3Q7IHdyb3RlOjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxi
cj4NCiZndDsgJmd0OyB2d3JhcC1ib3VuY2VzQGlldGYub3JnIHdyb3RlIG9uIDA1LzE3LzIwMTAg
MTA6MDg6MjYgQU06PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgW2ltYWdlIHJl
bW92ZWRdPGJyPg0KJmd0OyAmZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyBSZTogW3Z3cmFw
XSBWV1JBUCBhbmQgSVB2Njxicj4NCiZndDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsg
UmljaGFyZCBCYXJuZXM8YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IHRv
Ojxicj4NCiZndDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgTW9yZ2FpbmU8YnI+DQom
Z3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IDA1LzE3LzIwMTAgMTA6MDkgQU08YnI+
DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IFNlbnQgYnk6PGJyPg0KJmd0OyAm
Z3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyB2d3JhcC1ib3VuY2VzQGlldGYub3JnPGJyPg0K
Jmd0OyAmZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyBDYzo8YnI+DQomZ3Q7ICZndDsgJmd0
Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IHZ3cmFwPGJyPg0KJmd0OyAmZ3Q7ICZndDs8YnI+DQomZ3Q7
ICZndDsgJmd0OyBJbiB0aGUgc3Bpcml0IG9mIGdvb2QgbGF5ZXJpbmcsIGl0IHNlZW1zIGxpa2Ug
d2Ugc2hvdWxkDQpiZSB0YWxraW5nPGJyPg0KJmd0OyAmZ3Q7ICZndDsgYWJvdXQgYXZvaWRpbmcg
ZGlyZWN0IHJlbGlhbmNlIG9uIElQIGFkZHJlc3NlcyBpbnN0ZWFkIG9mDQpob3cgd2UgY2FuPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgYWNjb21tb2RhdGUgZGlmZmVyZW50IGFkZHJlc3NlcyBpbiB0aGUg
cHJvdG9jb2wuICZuYnNwO1doeQ0KaXMgdGhlcmUgJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IGV2ZXIg
YTxicj4NCiZndDsgJmd0OyAmZ3Q7IG5lZWQgdG8gY2FycnkgYW4gSVAgYWRkcmVzcyBpbiB0aGlz
IGFwcGxpY2F0aW9uLWxheWVyIHByb3RvY29sLA0KYXM8YnI+DQomZ3Q7ICZndDsgJmd0OyBvcHBv
c2VkIHRvLCBzYXksIGEgRE5TIG5hbWUgb3IgYSBVUkk/PGJyPg0KJmd0OyAmZ3Q7ICZndDs8YnI+
DQomZ3Q7ICZndDsgJmd0OyAtLVJpY2hhcmQ8YnI+DQomZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsg
Jmd0OyArMTxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBXZSBtYXkgZnJvbSB0aW1lIHRv
IHRpbWUgaGF2ZSBhIElQIGFkZHJlc3Mgc3R1Y2sgaW4gdGhlIGZvcm0NCm9mIGEgVVJJPGJyPg0K
Jmd0OyAmZ3Q7IHdoaWNoIGhhcyB0aGUgZG90dGVkIGRlY2ltYWwgZm9ybSBvZiBhbiByZXNvdXJj
ZS4gVGhlIHNwZWMgc2hvdWxkDQptYWtlPGJyPg0KJmd0OyAmZ3Q7IHN1cmUgdGhhdCBmb3JtIGNh
biBiZSBhbiBJUFY2IGFkZHJlc3MsIGJ1dCB0aGF0IHNob3VsZCBiZSB2ZXJ5DQombmJzcDs8YnI+
DQomZ3Q7ICZndDsgc3RyYWlnaHQ8YnI+DQomZ3Q7ICZndDsgZm9yd2FyZC48YnI+DQomZ3Q7ICZn
dDs8YnI+DQomZ3Q7ICZndDsgVGhlcmUgbWF5IGJlIHNvbWUgSVBWNiBmZWF0dXJlcyB3aGljaCBl
dmVudHVhbGx5IGltcGFjdCB1cyBhdA0KdGhlICZuYnNwOzxicj4NCiZndDsgJmd0OyBwcm90b2Nv
bDxicj4NCiZndDsgJmd0OyBkZXNpZ24gbGV2ZWwsIGJ1dCB0aGUgZW50aXJlIFZXUkFQIHNwZWNp
ZmljYXRpb24gaGFzIGJlZW4gd3JpdHRlbg0KaW4gJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7IHRlcm1z
IG9mPGJyPg0KJmd0OyAmZ3Q7IFVSSXMgYW5kIENhcGFiaWxpdGllcywgbm90IGluIHRlcm1zIG9m
IGxvdyBsZXZlbCBJUCBhZGRyZXNzZXMuDQpJdCAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgd291bGQg
dGFrZSBhbjxicj4NCiZndDsgJmd0OyBpbmNyZWRpYmx5IHBvd2VyZnVsIGFyZ3VtZW50IHRvIHN1
Z2dlc3QgdGhhdCB0aGlzIHNob3VsZCBjaGFuZ2UuDQombmJzcDs8YnI+DQomZ3Q7ICZndDsgTGlr
ZXdpc2UsIHdoaWxlPGJyPg0KJmd0OyAmZ3Q7IElQVjYgY2hhbmdlcyBhZGRyZXNzaW5nIGF0IHRo
ZSBib3R0b20gb2YgdGhlIHN0YWNrLCBpdCBkb2Vzbid0DQombmJzcDs8YnI+DQomZ3Q7ICZndDsg
YXBwcmVjaWFibHkgY2hhbmdlPGJyPg0KJmd0OyAmZ3Q7IHRoZSBjb3N0IG9mIGhvbGRpbmcgb3Bl
biBzZXNzaW9ucywgb2YgbWFuYWdpbmcgc29ja2V0cyBhbmQgYnVmZmVycw0KJm5ic3A7PGJyPg0K
Jmd0OyAmZ3Q7IGluc2lkZSBvZjxicj4NCiZndDsgJmd0OyBjbGllbnRzIChlc3BlY2lhbGx5IGxp
Z2h0d2VpZ2h0IGRldmljZXMpIEZ1cnRoZXIgd2hpbGUgd2UgY2FuDQphbGwgJm5ic3A7PGJyPg0K
Jmd0OyAmZ3Q7IGRldm91dGx5IGhvcGU8YnI+DQomZ3Q7ICZndDsgdGhhdCBJUFY2IGZpbmFsbHkg
ZGVwbG95cyBicm9hZGx5LCBtYWtpbmcgaXQgYSBkZXBlbmRhbmN5IGluDQp0aGUgJm5ic3A7PGJy
Pg0KJmd0OyAmZ3Q7IG5lYXIgdGVybSBmZWVsczxicj4NCiZndDsgJmd0OyByYXRoZXIgbGlrZSBh
IHJvYWRibG9jayB0byBwb3NzaWJsZSBhZG9wdGlvbi48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7
ICZndDsgLSBEYXZpZDxicj4NCiZndDsgJmd0OyB+IFpoYTxicj4NCiZndDsgJmd0Ozxicj4NCiZn
dDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7
ICZndDsgT24gTWF5IDE0LCAyMDEwLCBhdCA3OjMyIEFNLCBNb3JnYWluZSB3cm90ZTo8YnI+DQom
Z3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgRGVzcGl0ZSBleGNlZWRpbmds
eSBsb3cgdGFrZXVwIG9mIElQdjYgc28gZmFyLCBpdCdzDQpjb21pbmcsIGFuZCBpbjxicj4NCiZn
dDsgJmd0OyAmZ3Q7ICZndDsgdGhlIGNvbnRleHQgb2YgSUVURiBXRyByYXRlcyBvZiBwcm9ncmVz
cywgaXQgaXMgcmVhbGx5DQombmJzcDs8YnI+DQomZ3Q7ICZndDsgaW1taW5lbnQuICZuYnNwO09m
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBzcGVjaWFsIHJlbGV2YW5jZSB0byB1cyBpcyB0aGF0
IElQdjQgYWRkcmVzc2VzIGFyZQ0KcHJvamVjdGVkIHRvICZuYnNwOzxicj4NCiZndDsgJmd0OyBy
dW48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IG91dCB3aXRoaW4gcm91Z2hseSB0aGUgc2FtZSB0
aW1lIGZyYW1lIGFzIFZXUkFQIG1hdGVyaWFsaXplcy48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBUaGVyZSBpcyBsaXR0bGUgcG9pbnQgaW4gY3JlYXRp
bmcgYSBuZXcgVlcgcHJvdG9jb2wNCnRvZGF5IHB1cmVseSAmbmJzcDs8YnI+DQomZ3Q7ICZndDsg
aW48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IHRoZSBjb250ZXh0IG9mIElQdjQgd2l0aG91dCB0
aGlua2luZyBhYm91dCB0b21vcnJvdydzDQpJUHY2PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBl
bnZpcm9ubWVudC4gJm5ic3A7QnkgdGhlIHRpbWUgdGhhdCBWV1JBUCBpcyBmdWxseQ0KZGVmaW5l
ZCwgd2Ugc2hvdWxkPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBleHBlY3QgYSBzdWJzdGFudGlh
bCBhbmQgcmFwaWRseSBpbmNyZWFzaW5nIHByb3BvcnRpb24NCm9mIFZXUkFQPGJyPg0KJmd0OyAm
Z3Q7ICZndDsgJmd0OyBpbXBsZW1lbnRhdGlvbnMgdG8gb2NjdXIgaW4gSVB2Ni1hY2Nlc3NpYmxl
IHdvcmxkcy4NCiZuYnNwO1RoaXMgaXMgYTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgc2l0dWF0
aW9uIGZvciB3aGljaCB3ZSBuZWVkIHRvIHBsYW4gbm93LCBvdGhlcndpc2UNCnRoZSBwcm90b2Nv
bCAmbmJzcDs8YnI+DQomZ3Q7ICZndDsgd2lsbDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgYmUg
b2Jzb2xldGUgYmVmb3JlIGl0J3MgZXZlbiByZWFkeS48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBUbyBnZXQgdGhlIGJhbGwgcm9sbGluZywgaGVyZSBh
cmUgYSBmZXcgSVB2Ni1yZWxhdGVkDQppc3N1ZXMgdGhhdCAmbmJzcDs8YnI+DQomZ3Q7ICZndDsg
d2U8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGNvdWxkIHVzZWZ1bGx5IGFkZHJlc3MgaW4gdGhl
IGdyb3VwOjxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7
ICZuYnNwOyAmbmJzcDvigKIgVGhlIDEyOC1iaXQgSVAgYWRkcmVzcyBvZiBJUHY2IGlzIGxpa2Vs
eQ0KdG8gYmVjb21lIGEgY29tbW9uPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBwYXlsb2FkLCBz
byBpdCBzaG91bGQgYmUgc3VwcG9ydGVkIG5hdGl2ZWx5LiAmbmJzcDtMTFNEDQphbHJlYWR5ICZu
YnNwOzxicj4NCiZndDsgJmd0OyBzdXBwb3J0czxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgb25l
IDEyOC1iaXQgZGF0YSB0eXBlIG9mIGNvdXJzZSwgdGhlIFVVSUQuICZuYnNwO0lQdjYNCmFkZHJl
c3NlcyBzaG91bGQ8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IG5vdCBiZSB0cmFuc3BvcnRlZCBp
biBVVUlEIGZpZWxkcyBob3dldmVyLCBzaW5jZSB0aGVpcg0Kc3RhdGlzdGljYWw8YnI+DQomZ3Q7
ICZndDsgJmd0OyAmZ3Q7IHByb3BlcnRpZXMgYW5kIHNlbWFudGljcyBhcmUgdG90YWxseSBkaWZm
ZXJlbnQuICZuYnNwO0luDQphbnkgY2FzZSwgdGhlPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyB0
d28gc3BhY2VzIGFyZSBkaXNqb2ludCBzbyBjb25mdXNpbmcgdGhlbSB3b3VsZCBiZQ0KYSBtaXN0
YWtlLiAmbmJzcDtUaGU8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IElQdjYgYWRkcmVzcyBzZWVt
cyBhIGdvb2QgY2FuZGlkYXRlIGZvciBpdHMgb3duIGRlZmluZWQNCnR5cGUsIGluICZuYnNwOzxi
cj4NCiZndDsgJmd0OyB0aGU8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGFic2VuY2Ugb2Ygd2lk
ZSBpbnRlZ2Vycy48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDvigKIgVGhl
IGV4dHJlbWVseSBsYXJnZSBhZGRyZXNzIHNwYWNlIG9mDQpJUHY2IGhhcyBvZnRlbiBiZWVuPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBwb3J0cmF5ZWQgYXMgYWxsb3dpbmcgZXZlcnl0aGluZyBh
cm91bmQgdXMgdG8gaGF2ZQ0KaXRzIG93biBJUDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgYWRk
cmVzcy4gJm5ic3A7SW4gdGhlIGNvbnRleHQgb2YgdmlydHVhbCB3b3JsZHMsIHRoaXMNCmlkZWEg
Y2FuIGFjdHVhbGx5PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBiZSBwdXQgdG8gZ29vZCB1c2Us
IHdpdGggZWFjaCB2aXJ0dWFsIG9iamVjdCBiZWFyaW5nDQppdHMgb3duIElQdjY8YnI+DQomZ3Q7
ICZndDsgJmd0OyAmZ3Q7IGFkZHJlc3MuICZuYnNwO09uZSBjYW5kaWRhdGUgYXBwbGljYXRpb24g
Zm9yIHRoaXMgaGFzDQphbHJlYWR5IGJlZW48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGRlc2Ny
aWJlZCBpbiBlYXJsaWVyIGRpc2N1c3Npb25zIC0tLSBmb3IgZXhhbXBsZSwgaW1wbGVtZW50aW5n
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyB2aXJ0dWFsIG9iamVjdCBzaW11bGF0aW9uIGluIHR3
byBwYXJ0cywgb25lIGNsaWVudC1zaWRlDQphbmQgb25lPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0
OyB3b3JsZC1zaWRlLCB0aGUgdHdvIHBhcnRzIGNvbW11bmljYXRpbmcgZGlyZWN0bHkuICZuYnNw
O0lQdjYNCmFkZHJlc3Npbmc8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IG9mIG9iamVjdHMgbWFr
ZXMgdGhpcyByZWxhdGl2ZWx5IGVhc3kgdG8gYWNoaWV2ZSBlZmZpY2llbnRseSwNCnNvICZuYnNw
Ozxicj4NCiZndDsgJmd0OyBpdHM8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGltcGxlbWVudGF0
aW9uIGluIElQdjYtYmFzZWQgd29ybGRzIGlzIGFsbW9zdCBpbmV2aXRhYmxlDQpiZWZvcmU8YnI+
DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGxvbmcuICZuYnNwO1ZXUkFQIHNob3VsZCBiZSByZWFkeSBm
b3IgdGhpcy48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDvigKIgVGhlIGV2
ZW50IHF1ZXVlIGluIGN1cnJlbnQgaW1wbGVtZW50YXRpb25zDQpwcm92aWRlcyBhbiAmbmJzcDs8
YnI+DQomZ3Q7ICZndDsgaW5kaXJlY3Q8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGFuZCBoaWdo
bHkgaW5lZmZpY2llbnQgd2F5IG9mIGFjaGlldmluZyB3b3JsZC10by1jbGllbnQ8YnI+DQomZ3Q7
ICZndDsgJmd0OyAmZ3Q7IGNvbW11bmljYXRpb25zLiAmbmJzcDtJUHY2IG9mZmVycyBvcHBvcnR1
bml0aWVzIGZvcg0KZGlyZWN0ICZuYnNwOzxicj4NCiZndDsgJmd0OyBjb21tdW5pY2F0aW9uPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyB0aGF0IGNhbiBtYWtlIHRoZSBldmVudCBxdWV1ZSBhcHBy
b2FjaCBvYnNvbGV0ZSwgc28NCml0J3Mgd29ydGg8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGV4
YW1pbmluZyBJUHY2LW9yaWVudGVkIGFsdGVybmF0aXZlcy48YnI+DQomZ3Q7ICZndDsgJmd0OyAm
Z3Q7ICZuYnNwOyAmbmJzcDvigKIgV2UgcmVjZW50bHkgZGlzY3Vzc2VkIGZlYXR1cmUgYW5kIHBy
b3RvY29sDQpuZWdvdGlhdGlvbiB3aXRoaW48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IFZXUkFQ
LiAmbmJzcDtJUHY2IHByb3ZpZGVzIG11Y2ggb3Bwb3J0dW5pdHkgZm9yIG5ldw0KZmVhdHVyZXMg
YW5kICZuYnNwOzxicj4NCiZndDsgJmd0OyBwcm90b2NvbDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZn
dDsgcGF0aHdheXMgdG8gYmUgbmVnb3RpYXRlZCBiZXR3ZWVuIGVuZHBvaW50cywgc28gaXQNCmdp
dmVzIHVzIGEgdmVyeTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgcmVhbCBhbmQgaW1taW5lbnQg
c2V0IG9mIHVzZSBjYXNlcyBmb3IgbmVnb3RpYXRpb24uPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0
Ozxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgSXQgd291bGQgYWxzbyBiZSBhIGZlYXRoZXIgaW4g
VldSQVAncyBjYXAgdG8gYmUgY29uc2lkZXJlZA0KYW4gJm5ic3A7PGJyPg0KJmd0OyAmZ3Q7ICZx
dW90O0lQdjYtPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBjYXBhYmxlIGFwcGxpY2F0aW9uIHBy
b3RvY29sJnF1b3Q7IGluIGEgc3Ryb25nZXIgc2Vuc2UNCnRoYW4ganVzdCB0byBiZTxicj4NCiZn
dDsgJmd0OyAmZ3Q7ICZndDsgY2FycmllZCBieSBJUHY2IG5ldHdvcmtzLiAmbmJzcDtJUHY2IGRv
ZXMgYWZ0ZXIgYWxsDQpicmluZyBuZXcgYWJpbGl0aWVzPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0
OyB0byB0aGUgdGFibGUsIHN1Y2ggYXMgdGhlIGh1Z2UgYWRkcmVzc2luZywgYW5kIGl0IHdvdWxk
DQpiZSBhICZuYnNwOzxicj4NCiZndDsgJmd0OyBtaXN0YWtlPGJyPg0KJmd0OyAmZ3Q7ICZndDsg
Jmd0OyB0byBpZ25vcmUgdGhlbS48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAm
Z3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgTW9yZ2FpbmUuPGJyPg0KJmd0
OyAmZ3Q7ICZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsg
Jmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgdndyYXAg
bWFpbGluZyBsaXN0PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyB2d3JhcEBpZXRmLm9yZzxicj4N
CiZndDsgJmd0OyAmZ3Q7ICZndDsgPC9mb250PjwvdHQ+PGEgaHJlZj1odHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Z3cmFwPjx0dD48Zm9udCBzaXplPTI+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92d3JhcDwvZm9udD48L3R0PjwvYT48dHQ+PGZvbnQg
c2l6ZT0yPjxicj4NCiZndDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQomZ3Q7ICZndDsgJmd0
OyB2d3JhcCBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7ICZndDsgJmd0OyB2d3JhcEBpZXRmLm9yZzxi
cj4NCiZndDsgJmd0OyAmZ3Q7IDwvZm9udD48L3R0PjxhIGhyZWY9aHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby92d3JhcD48dHQ+PGZvbnQgc2l6ZT0yPmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXA8L2ZvbnQ+PC90dD48L2E+PHR0Pjxmb250IHNp
emU9Mj48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQomZ3Q7ICZndDsgdndyYXAgbWFpbGluZyBs
aXN0PGJyPg0KJmd0OyAmZ3Q7IHZ3cmFwQGlldGYub3JnPGJyPg0KJmd0OyAmZ3Q7IDwvZm9udD48
L3R0PjxhIGhyZWY9aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92d3JhcD48
dHQ+PGZvbnQgc2l6ZT0yPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndy
YXA8L2ZvbnQ+PC90dD48L2E+PHR0Pjxmb250IHNpemU9Mj48YnI+DQomZ3Q7ICZndDs8YnI+DQom
Z3Q7ICZndDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188
YnI+DQomZ3Q7ICZndDsgdndyYXAgbWFpbGluZyBsaXN0PGJyPg0KJmd0OyAmZ3Q7IHZ3cmFwQGll
dGYub3JnPGJyPg0KJmd0OyAmZ3Q7IDwvZm9udD48L3R0PjxhIGhyZWY9aHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92d3JhcD48dHQ+PGZvbnQgc2l6ZT0yPmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXA8L2ZvbnQ+PC90dD48L2E+PHR0Pjxmb250
IHNpemU9Mj48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQomZ3Q7ICZndDsgdndyYXAgbWFpbGlu
ZyBsaXN0PGJyPg0KJmd0OyAmZ3Q7IHZ3cmFwQGlldGYub3JnPGJyPg0KJmd0OyAmZ3Q7IDwvZm9u
dD48L3R0PjxhIGhyZWY9aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92d3Jh
cD48dHQ+PGZvbnQgc2l6ZT0yPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
dndyYXA8L2ZvbnQ+PC90dD48L2E+PHR0Pjxmb250IHNpemU9Mj48YnI+DQomZ3Q7ICZndDs8YnI+
DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX188YnI+DQomZ3Q7ICZndDsgdndyYXAgbWFpbGluZyBsaXN0PGJyPg0K
Jmd0OyAmZ3Q7IHZ3cmFwQGlldGYub3JnPGJyPg0KJmd0OyAmZ3Q7IDwvZm9udD48L3R0PjxhIGhy
ZWY9aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92d3JhcD48dHQ+PGZvbnQg
c2l6ZT0yPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXA8L2ZvbnQ+
PC90dD48L2E+PHR0Pjxmb250IHNpemU9Mj48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDs8
YnI+DQomZ3Q7ICZndDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX188YnI+DQomZ3Q7ICZndDsgdndyYXAgbWFpbGluZyBsaXN0PGJyPg0KJmd0OyAmZ3Q7IHZ3
cmFwQGlldGYub3JnPGJyPg0KJmd0OyAmZ3Q7IDwvZm9udD48L3R0PjxhIGhyZWY9aHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92d3JhcD48dHQ+PGZvbnQgc2l6ZT0yPmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXA8L2ZvbnQ+PC90dD48L2E+PHR0
Pjxmb250IHNpemU9Mj48YnI+DQomZ3Q7IDxicj4NCiZndDsgX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQomZ3Q7IHZ3cmFwIG1haWxpbmcgbGlzdDxi
cj4NCiZndDsgdndyYXBAaWV0Zi5vcmc8YnI+DQomZ3Q7IDwvZm9udD48L3R0PjxhIGhyZWY9aHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92d3JhcD48dHQ+PGZvbnQgc2l6ZT0y
Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdndyYXA8L2ZvbnQ+PC90dD48
L2E+PHR0Pjxmb250IHNpemU9Mj48YnI+DQo8L2ZvbnQ+PC90dD4NCg==
--=_alternative 005652F785257729_=--

From morgaine.dinova@googlemail.com  Thu May 20 09:31:35 2010
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3C2A3A6B80 for <vwrap@core3.amsl.com>; Thu, 20 May 2010 09:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.229
X-Spam-Level: 
X-Spam-Status: No, score=0.229 tagged_above=-999 required=5 tests=[AWL=0.716,  BAYES_05=-1.11, 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 QSOuk4nzPRCh for <vwrap@core3.amsl.com>; Thu, 20 May 2010 09:31:31 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id A98DF3A68AE for <vwrap@ietf.org>; Thu, 20 May 2010 09:31:30 -0700 (PDT)
Received: by wwb24 with SMTP id 24so1684993wwb.31 for <vwrap@ietf.org>; Thu, 20 May 2010 09:31:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=o3p0C9yL7tBTuvwjhH0VJ7PlIHPLs90MMPHA92Rbh4w=; b=uHaXw58GWc2i9qpcw8srV4qVk8C0dU4duCARftANlN3aIZYdu74lwubP2KxS9lBQWV oudIpdAFcC6jZNVVzvYGuv0HlONhz4kOF5S1AGvxRiGx0drNVNcrICCCRzsnk3HlUxbZ FfIouHiHTs2q4PjJwxyFlgBNZLZMrnoWKNlTU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=iI03zlcXYR90EYtGNZ9zDXvmgsSLv9tpULXesh6UR+fTurPSPL2lgafJlCN5MiDNu2 EOgvqkEMq70qI7+aZugFtqmiN4Urae7MLnCvjC8Q7nQ7DNOm/X8NXcONCaifzgPVtpNu LjCo8tl8/y1GT+XTdd4nN32f4CIhpOv+78sFE=
MIME-Version: 1.0
Received: by 10.216.165.75 with SMTP id d53mr66763wel.76.1274373079148; Thu,  20 May 2010 09:31:19 -0700 (PDT)
Received: by 10.216.26.132 with HTTP; Thu, 20 May 2010 09:31:19 -0700 (PDT)
In-Reply-To: <18CBEFBB-3356-4CD0-BBFF-266672322621@bbn.com>
References: <AANLkTik75YvP5y_F68_TxXbPBaN1fnYcXk5JPkfM5uRE@mail.gmail.com> <OFC2E23B0D.5B99CD05-ON85257726.0050CDA0-85257726.00518F0E@us.ibm.com> <AANLkTikINIWeYP9pqIeTtNzfD5wrf07ADkCwkNcVQZk4@mail.gmail.com> <A32EAB16-62A5-4307-A320-0187955BFA51@bbn.com> <AANLkTimY7viwIMzFIIX_-OzZjA-jHsiK35EF4OpdnAxW@mail.gmail.com> <632C4898-F7DD-4B76-AAFB-D675346E2521@gmail.com> <AANLkTik42H1xhnr_yljo06-4thbaT3GcLBDabzoj2c2t@mail.gmail.com> <B2E410EF-1AD1-45E6-88A3-BE18FCC1571F@bbn.com> <AANLkTikqBQPp-o_u58tas669x55n7bZ1R3oXSoaG2q3Z@mail.gmail.com> <18CBEFBB-3356-4CD0-BBFF-266672322621@bbn.com>
Date: Thu, 20 May 2010 17:31:19 +0100
Message-ID: <AANLkTilD80paAW0Ox0Q3lz9jcjRCBIBZj9T_E9HYIeyN@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary=0016e6497e96b1a9430487091a65
Subject: Re: [vwrap] VWRAP and IPv6
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 16:31:35 -0000

--0016e6497e96b1a9430487091a65
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

It wasn't intended as a debate, Richard, only as a heads-up of what's
coming.  We each have our own individual interests, and the intersection of
VWs and IPv6 may not be one of yours ---  that's perfectly fine of course.
:-)

But IPv6 is coming.  /64's for everyone are coming.  The desire to scale VW=
s
is coming.  The need to reduce or eliminate overheads where technology
allows is coming too, and IPv6's huge assigned user address blocks allow
exactly that.  Some virtual worlds will take advantage of this important
facility, and hence are likely to scale far better than those that don't.

I looked at Dave Thaler's slides, but there's very little there on this
topic.  The advice "user applications should use names rather than
addresses" is very good advice indeed, but Dave prefixed it very sensibly
with "In general" because it does not apply in all cases.  In particular, i=
t
does not apply where there are no names, nor where IP addresses are
generated dynamically.

I gave a practical example of this in my previous post.  When an ICO is
generated dynamically in a client, there is no corresponding domain name
that can be looked up, so a dynamic name would have to be manufactured to
comply with a "must have names" dogma.  There might actually be a good
technical (and non-dogmatic) reason for indirection by name at that level.
If so then it would have to be examined, in the usual engineering way.

Notice however that dynamic name lookups don't make IP addresses disappear.
If we provide an IWO with a name abstraction to denote an ICO's IPv6
address, then the IWO would acquire the ICO's address by lookup.  The IWO
could then make the very efficient direct connection to its corresponding
IPv6 peer on the client.  The use of name lookups just affects IP address
acquisition, it doesn't change the IWO-ICO connection architecture.

Notice that this fits into our REST-like model very cleanly.  A REST
resource could be provided in the client, acting as a container which
indexes local ICOs by the name (URI) of their corresponding IWO.  An IWO
could then easily request any ICO metadata it needs, including the IPv6
address of its peer ICO, prior to establishing a direct connection to it.


Morgaine.




=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

On Thu, May 20, 2010 at 4:19 PM, Richard Barnes <rbarnes@bbn.com> wrote:

> I'm losing interest in this debate, and I think we've all said our piece,
> so I'll just close with a reference to the venerable RFC 1958,
> "Architectural Principles of the Internet":
> "
>   In general, user applications should use names rather than addresses.
> "
> (taken from a nice presentation that Dave Thaler gave on how pathological
> IP addresses can be:)
> <http://www.ietf.org/proceedings/73/slides/plenaryw-1.pdf>
>
> Feel free to use IPv6 addresses in the application layer if you want, but
> be aware that there be dragons.
>
> --Richard
>
>
>
> On May 20, 2010, at 10:46 AM, Morgaine wrote:
>
>  Abstracting over addresses is fine, Richard, but after you've dealt with
>> the abstractions you typically end up with addresses, and that's what
>> protocols work with from then on.
>>
>> The textual abstractions are only there for human comfort, ease of
>> configuration, and great flexibility of indirection, but abstractions ar=
e
>> just means to an end.  After the address abstractions are de-abstracted,
>> protocols work with the much more efficient binary representations.  Tha=
t's
>> practically universal.
>>
>> It's easy to give a practical example of such operation.  For example,
>> consider a design in which all VW objects have two parts, an in-world ob=
ject
>> (IWO) and an in-client object (ICO), where the ICO is replicated in each
>> client.  Let both parts be active, ie. both sides can be event generator=
s.
>>  It's easy for ICOs to address update events to their IWO because there =
is
>> only one IWO, and access could be optimized to network level after the
>> de-abstraction step for efficiency.  But what about updates in the rever=
se
>> direction, which is 1:N?
>>
>> In the typical IPv4 environment, the usual approach would be a heavily
>> indirected one, with updates travelling through layer upon layer of
>> middleware before reaching their target ICO.  In an IPv6 environment in
>> which each ICO can have its own IPv6 address, there need be no middlewar=
e at
>> all between the host kernel and the target object.  The resulting increa=
se
>> in efficiency by orders of magnitude can have major ramifications on the
>> operation of your world and of your clients.
>>
>> And the cost of this massive leap in efficiency?  Merely to inform the I=
WO
>> of the ICO's dynamic IPv6 network address, which borders on the trivial.
>>
>> One of my main interests is VW scalability, both of worlds and of client=
s,
>> and such efficiency gains are truly important.  Scaling VW complexity an=
d
>> rendering of crowds or of highly detailed visualizations requires some
>> lateral thinking and more powerful networking paradigms than we have bee=
n
>> used to until now.  IPv6 offers some interesting solutions in that
>> direction, and they will be used.
>>
>>
>> Morgaine.
>>
>>
>>
>>
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> On Thu, May 20, 2010 at 2:43 PM, Richard Barnes <rbarnes@bbn.com> wrote:
>> As an aside, there's nothing that says that subscribers have to be
>> allocated a /64.  Some proposed addressing schemes that are more
>> conservative (in the Asia/Pacific region IIRC) actually assign much long=
er
>> prefixes (smaller address blocks) to customers.
>>
>> Fine-grained addressability is not the same as fine-grained allocation o=
f
>> *IP* addresses. Think of it this way: HTTP has very fine-grained
>> addressability, with individual identifier/locators for pages, images,
>> scripts, etc.  It's able to accomplish this not by assigning an IPv6 add=
ress
>> to every object, but by using an application-layer identifier/locator --
>> namely a URL.
>>
>> Not using IPv6 addresses in applications is not painting oneself into an
>> IPv4 corner, it's good protocol design following the layering model of t=
he
>> Internet.  (If we're using IPv4 addresses for identifiers, we shouldn't =
be
>> doing that either!)  Abstracting over IP addresses is about freeing the
>> application from having to worry about whether its IPv4 or IPv6 or IPv10=
 or
>> X.25 or whatever else at the network layer.
>>
>> --Richard
>>
>>
>>
>>
>> On May 20, 2010, at 9:23 AM, Morgaine wrote:
>>
>> On Thu, May 20, 2010 at 10:59 AM, Han Sontse <han.sontse.sl@gmail.com>
>> wrote:
>> I recognize that it is temping to take advantage of the huge address spa=
ce
>> that IPv6 offers but my test engineer instincts tell me it is unwise to =
do
>> so.
>>
>>
>> I too am an engineer, but solid engineering instincts do not tell us to
>> use only those facilities whose numbers or sizes can be tested exhaustiv=
ely.
>>  If it were so, we would not have multi-terabyte disk drives today.
>>
>> The /64 minimum routable subnet of IPv6 address space was not designed a=
s
>> it was because people were expected to need 2^64 NIC cards in their PCs.
>>  This immense per-user address block was created because IPv6 designers
>> could see beyond IPv4's use of addresses for host interface identificati=
on,
>> and were visionary enough to realize that all objects could benefit from
>> network addressability.  This also happens to be one of the key messages=
 of
>> REST.  Addressability is extremely important, the finer the better, not =
only
>> on the Web, and not only with URIs.
>>
>> With IPv6 just around the corner, I foresee such addressability at fine
>> levels of granularity appearing in VWs relatively soon.  IPv4 worlds wil=
l
>> have to emulate what IPv6 worlds achieve natively, and that is the right=
 way
>> around.  When legacy design restricts progress, the only thing it achiev=
es
>> is rapid obsolescence.
>>
>> I would prefer VWRAP not to be painting itself into an IPv4 corner of
>> obsolescence before it's even released, which is why I'm raising this to=
pic
>> --- it's intended as a heads-up for the group.
>>
>> Since the rise of VWs and IPv6 take-up are going to occur concurrently, =
I
>> think the next few years are going to be very interesting on the VW
>> networking front.  My recommendation is to observe carefully what happen=
s,
>> and not to make any rash decisions based on legacy ideas that could cut =
off
>> your future.
>>
>>
>> Morgaine.
>>
>>
>>
>>
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> On Thu, May 20, 2010 at 10:59 AM, Han Sontse <han.sontse.sl@gmail.com>
>> wrote:
>> It's a bad idea to use IP addresses for anything other than addressing a
>> machine level interface.  Using them to interface objects at or above th=
e
>> application level is asking for trouble.   UUIDs are UUIDs... IP address=
es
>> are IP addresses.   The two should not be mixed.   I recognize that it i=
s
>> temping to take advantage of the huge address space that IPv6 offers but=
 my
>> test engineer instincts tell me it is unwise to do so.
>>
>> Han.
>>
>> On May 20, 2010, at 2:50 AM, Morgaine wrote:
>>
>> A /64 is the smallest routable IPv6 subnet, hence there is no extra
>> routing overhead for the 2^(128-64) addresses in the basic block that ev=
ery
>> user will have allocated.
>>
>> Needless to say, there won't be anything like 2^64 objects in your
>> scenegraph, so if you use your IPv6 address space to address every
>> scenegraph object that you have instantiated client-side, you will still
>> have an extremely sparsely used /64 block.  You'll be keeping track of w=
hich
>> addresses you have assigned dynamically of course. (An address space of =
this
>> size is not linearly scannable in realistic time.)
>>
>> In principle this is no different to using UUIDs --- your IPv6
>> micro-servers will have unguessable IPv6 addresses within your /64 block=
,
>> and it'll be up to you to tell other participants in the protocol (for
>> example server-side objects) with which of your IPv6 micro-servers they =
are
>> to communicate.  This is why an ADT that is supportive of IPv6 operation
>> needs to be able to carry such data efficiently --- the UUID is no longe=
r
>> the only 128-bit datum of interest.
>>
>> Of course your entire /64 block is routed as one, since there are no
>> smaller routable subnets in IPv6, and therefore your objections about
>> routing non-scalability do not apply.
>>
>>
>> Morgaine.
>>
>>
>>
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> On Wed, May 19, 2010 at 10:56 PM, Richard Barnes <rbarnes@bbn.com> wrote=
:
>> The impact of IPv6 on VWs should be far less than you imagine, I think. =
:)
>>
>> It has often been said that many, many things will be assigned IPv6
>> addresses.  There will certainly be enough to go around, but that doesn'=
t
>> make them good application-layer identifiers.  If you want to use IP
>> addresses with IP, they have to route, and that means that they have to =
be
>> either (1) topologically assigned, or (2) overlay routed, e.g., with mob=
ile
>> IP.  So if you want to use an IP address to address something, you're go=
ing
>> to have to either change that address when the thing gets connected
>> differently, or you'll need some overlay routing scheme to route to a
>> persistent address.  (And if you're not going to use the address with IP=
,
>> then why would you use an IP address?)
>>
>> VWRAP, as an application layer protocol, has a choice about what
>> identifiers to use for things and how to use those identifiers.  ISTM th=
at
>> using IP addresses (again, of either type) remains a bad idea, compared =
with
>> something that is decoupled from the routing layer.
>>
>> As far as the DNS, I'm not sure what your point is:
>> (i) DNS caching has been around for decades
>> (ii) DNS names can already refer to multiple addresses
>> (iii) Depends on implementation.  Maybe there's some application-layer w=
ay
>> to resolve names.  E.g., SIP endpoints don't need to have DNS records
>> because the INVITE transaction maps from SIP URIs to IP addresses.
>> (iv) From RFC 4291: "IPv6 addresses are 128-bit identifiers for interfac=
es
>> and sets of
>> interfaces"
>> (v) Seems like there's a use case lurking, hard to address without
>> details.  But you're probably still at the application layer.  For insta=
nce,
>> if you were telling your peer to send you an HTTP request, you would sen=
d an
>> HTTP URI, which can already handle IPv6 addresses.
>>
>> --Richard
>>
>>
>>
>> On May 19, 2010, at 9:35 AM, Morgaine wrote:
>>
>> The impact of IPv6 on VWs is going to be far greater than you imagine, I
>> believe.  As things stand, VWRAP is being designed around the features a=
nd
>> limitations of IPv4 networking.  It will of course be able to ride on to=
p of
>> IPv6 as a transport, but unable to benefit from its improved feature set=
,
>> unless we provide the means to do so.
>>
>> The question "Why is there ever a need to carry an IP address in this
>> application-layer protocol, as opposed to, say, a DNS name or a URI?"
>> suggests an IPv4 mindset, because in IPv6 it has a variety of possible
>> answers:  (i) When the DNS lookup has already been done and does not nee=
d to
>> be done again, (ii) When a FQDN maps to multiple addresses, but you want=
 to
>> refer to a specific one, (iii) When an IPv6 address does not have an
>> external address record, (iv) When the host is already known and the IP
>> address denotes something other than a physical NIC interface, or (v) Wh=
en
>> listeners are allocated locally and dynamically for the current session
>> only, and their IP addresses need to be communicated to a peer --- this =
will
>> be an extremely common use case with IPv6.
>>
>> In today's IPv4-based systems, it is normal for a user's machine to have=
 a
>> single IP address, and for a client on that machine to talk to a server =
that
>> has a single customer-facing IP address too (although it may also have
>> others that are not public).  In IPv6-based systems, this simple scenari=
o is
>> still possible but represents only a special case among a new and vastly
>> expanded set of IPv6 use cases.
>>
>> The smallest allocatable block of IPv6 address space is a /64, so
>> 2^(128-64) IP addresses is the number that most normal IPv6 users will h=
ave,
>> although the much larger /48 blocks of 2^80 addresses are commonly assig=
ned
>> to users as well.  With such IP riches client-side, it is certain that t=
hey
>> will be used for something, and the obvious suggestion is to give every =
VW
>> object an IPv6 address of its own.
>>
>> Lest we forget, one of the most important properties of the REST paradig=
m
>> is addressability, but the benefits of high addressability go far beyond=
 the
>> Web.  This is a property that will become ubiquitous throughout networke=
d
>> computing with IPv6.  It's probably no exaggeration to say that *everyth=
ing*
>> will be getting its own IP address. :-)
>>
>> Faced with that future, it's a mistake to think in IPv4 terms and consid=
er
>> IPv6 addresses as merely denoting a host which can be obtained from its
>> FQDN.  That's IPv4 thinking, and represents only a very basic use case f=
or
>> IPv6.  In more extended use cases, IPv6 addresses will become much more =
like
>> active local UUIDs than like today's host IP addresses.  They will be us=
ed
>> for inner-application addressing, for example to make every object in an
>> application an addressable micro-server.
>>
>> VWRAP is being born into an IPv6 world, and it would be a mistake to
>> hardwire IPv4 thinking into its design.  We continually refer to the nee=
d
>> for extensibility and a desire to future-proof the protocol, but lip ser=
vice
>> is not enough.  Adding IPv6 addresses to the underlying ADT would provid=
e a
>> bare minimum level of thinking ahead to support VWRAP implementations th=
at
>> embrace large numbers of communicating objects.  (A generally extensible=
 ADT
>> would of course achieve the same thing, and more.)
>>
>>
>> Morgaine.
>>
>>
>>
>>
>>
>>
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> On Mon, May 17, 2010 at 3:50 PM, David W Levine <dwl@us.ibm.com> wrote:
>>
>>
>> vwrap-bounces@ietf.org wrote on 05/17/2010 10:08:26 AM:
>>
>> > [image removed]
>> >
>> > Re: [vwrap] VWRAP and IPv6
>> >
>> > Richard Barnes
>> >
>> > to:
>> >
>> > Morgaine
>> >
>> > 05/17/2010 10:09 AM
>> >
>> > Sent by:
>> >
>> > vwrap-bounces@ietf.org
>> >
>> > Cc:
>> >
>> > vwrap
>> >
>> > In the spirit of good layering, it seems like we should be talking
>> > about avoiding direct reliance on IP addresses instead of how we can
>> > accommodate different addresses in the protocol.  Why is there ever a
>> > need to carry an IP address in this application-layer protocol, as
>> > opposed to, say, a DNS name or a URI?
>> >
>> > --Richard
>> >
>> +1
>>
>> We may from time to time have a IP address stuck in the form of a URI
>> which has the dotted decimal form of an resource. The spec should make
>> sure that form can be an IPV6 address, but that should be very straight
>> forward.
>>
>> There may be some IPV6 features which eventually impact us at the protoc=
ol
>> design level, but the entire VWRAP specification has been written in ter=
ms
>> of
>> URIs and Capabilities, not in terms of low level IP addresses. It would
>> take an
>> incredibly powerful argument to suggest that this should change. Likewis=
e,
>> while
>> IPV6 changes addressing at the bottom of the stack, it doesn't appreciab=
ly
>> change
>> the cost of holding open sessions, of managing sockets and buffers insid=
e
>> of
>> clients (especially lightweight devices) Further while we can all devout=
ly
>> hope
>> that IPV6 finally deploys broadly, making it a dependancy in the near te=
rm
>> feels
>> rather like a roadblock to possible adoption.
>>
>> - David
>> ~ Zha
>>
>>
>>
>> >
>> > On May 14, 2010, at 7:32 AM, Morgaine wrote:
>> >
>> > > Despite exceedingly low takeup of IPv6 so far, it's coming, and in
>> > > the context of IETF WG rates of progress, it is really imminent.  Of
>> > > special relevance to us is that IPv4 addresses are projected to run
>> > > out within roughly the same time frame as VWRAP materializes.
>> > >
>> > > There is little point in creating a new VW protocol today purely in
>> > > the context of IPv4 without thinking about tomorrow's IPv6
>> > > environment.  By the time that VWRAP is fully defined, we should
>> > > expect a substantial and rapidly increasing proportion of VWRAP
>> > > implementations to occur in IPv6-accessible worlds.  This is a
>> > > situation for which we need to plan now, otherwise the protocol will
>> > > be obsolete before it's even ready.
>> > >
>> > > To get the ball rolling, here are a few IPv6-related issues that we
>> > > could usefully address in the group:
>> > >
>> > >    =95 The 128-bit IP address of IPv6 is likely to become a common
>> > > payload, so it should be supported natively.  LLSD already supports
>> > > one 128-bit data type of course, the UUID.  IPv6 addresses should
>> > > not be transported in UUID fields however, since their statistical
>> > > properties and semantics are totally different.  In any case, the
>> > > two spaces are disjoint so confusing them would be a mistake.  The
>> > > IPv6 address seems a good candidate for its own defined type, in the
>> > > absence of wide integers.
>> > >    =95 The extremely large address space of IPv6 has often been
>> > > portrayed as allowing everything around us to have its own IP
>> > > address.  In the context of virtual worlds, this idea can actually
>> > > be put to good use, with each virtual object bearing its own IPv6
>> > > address.  One candidate application for this has already been
>> > > described in earlier discussions --- for example, implementing
>> > > virtual object simulation in two parts, one client-side and one
>> > > world-side, the two parts communicating directly.  IPv6 addressing
>> > > of objects makes this relatively easy to achieve efficiently, so its
>> > > implementation in IPv6-based worlds is almost inevitable before
>> > > long.  VWRAP should be ready for this.
>> > >    =95 The event queue in current implementations provides an indire=
ct
>> > > and highly inefficient way of achieving world-to-client
>> > > communications.  IPv6 offers opportunities for direct communication
>> > > that can make the event queue approach obsolete, so it's worth
>> > > examining IPv6-oriented alternatives.
>> > >    =95 We recently discussed feature and protocol negotiation within
>> > > VWRAP.  IPv6 provides much opportunity for new features and protocol
>> > > pathways to be negotiated between endpoints, so it gives us a very
>> > > real and imminent set of use cases for negotiation.
>> > >
>> > > It would also be a feather in VWRAP's cap to be considered an "IPv6-
>> > > capable application protocol" in a stronger sense than just to be
>> > > carried by IPv6 networks.  IPv6 does after all bring new abilities
>> > > to the table, such as the huge addressing, and it would be a mistake
>> > > to ignore them.
>> > >
>> > >
>> > > Morgaine.
>> > >
>> > >
>> > >
>> > > _______________________________________________
>> > > vwrap mailing list
>> > > vwrap@ietf.org
>> > > https://www.ietf.org/mailman/listinfo/vwrap
>> >
>> > _______________________________________________
>> > vwrap mailing list
>> > vwrap@ietf.org
>> > https://www.ietf.org/mailman/listinfo/vwrap
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>>
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>>
>
>

--0016e6497e96b1a9430487091a65
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

It wasn&#39;t intended as a debate, Richard, only as a heads-up of what&#39=
;s coming.=A0 We each have our own individual interests, and the intersecti=
on of VWs and IPv6 may not be one of yours ---=A0 that&#39;s perfectly fine=
 of course.=A0 :-)<br>
<br>But IPv6 is coming.=A0 /64&#39;s for everyone are coming.=A0 The desire=
 to scale VWs is coming.=A0 The need to reduce or eliminate overheads where=
 technology allows is coming too, and IPv6&#39;s huge assigned user address=
 blocks allow exactly that.=A0 Some virtual worlds will take advantage of t=
his important facility, and hence are likely to scale far better than those=
 that don&#39;t.<br>
<br>I looked at Dave Thaler&#39;s slides, but there&#39;s very little there=
 on this topic.=A0 The advice &quot;user applications should use names rath=
er than addresses&quot; is very good advice indeed, but Dave prefixed it ve=
ry sensibly with &quot;In general&quot; because it does not apply in all ca=
ses.=A0 In particular, it does not apply where there are no names, nor wher=
e IP addresses are generated dynamically.<br>
<br>I gave a practical example of this in my previous post.=A0 When an ICO =
is generated dynamically in a client, there is no corresponding domain name=
 that can be looked up, so a dynamic name would have to be manufactured to =
comply with a &quot;must have names&quot; dogma.=A0 There might actually be=
 a good technical (and non-dogmatic) reason for indirection by name at that=
 level.=A0 If so then it would have to be examined, in the usual engineerin=
g way.<br>
<br>Notice however that dynamic name lookups don&#39;t make IP addresses di=
sappear.=A0 If we provide an IWO with a name abstraction to denote an ICO&#=
39;s IPv6 address, then the IWO would acquire the ICO&#39;s address by look=
up.=A0 The IWO could then make the very efficient direct connection to its =
corresponding IPv6 peer on the client.=A0 The use of name lookups just affe=
cts IP address acquisition, it doesn&#39;t change the IWO-ICO connection ar=
chitecture.<br>
<br>Notice that this fits into our REST-like model very cleanly.=A0 A REST =
resource could be provided in the client, acting as a container which index=
es local ICOs by the name (URI) of their corresponding IWO.=A0 An IWO could=
 then easily request any ICO metadata it needs, including the IPv6 address =
of its peer ICO, prior to establishing a direct connection to it.<br>
<br><br>Morgaine.<br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br><=
div class=3D"gmail_quote">On Thu, May 20, 2010 at 4:19 PM, Richard Barnes <=
span dir=3D"ltr">&lt;<a href=3D"mailto:rbarnes@bbn.com">rbarnes@bbn.com</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I&#39;m losing in=
terest in this debate, and I think we&#39;ve all said our piece, so I&#39;l=
l just close with a reference to the venerable RFC 1958, &quot;Architectura=
l Principles of the Internet&quot;:<br>

&quot;<br>
 =A0 In general, user applications should use names rather than addresses.<=
br>
&quot;<br>
(taken from a nice presentation that Dave Thaler gave on how pathological I=
P addresses can be:)<br>
&lt;<a href=3D"http://www.ietf.org/proceedings/73/slides/plenaryw-1.pdf" ta=
rget=3D"_blank">http://www.ietf.org/proceedings/73/slides/plenaryw-1.pdf</a=
>&gt;<br>
<br>
Feel free to use IPv6 addresses in the application layer if you want, but b=
e aware that there be dragons.<br><font color=3D"#888888">
<br>
--Richard</font><div><div></div><div class=3D"h5"><br>
<br>
<br>
On May 20, 2010, at 10:46 AM, Morgaine wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Abstracting over addresses is fine, Richard, but after you&#39;ve dealt wit=
h the abstractions you typically end up with addresses, and that&#39;s what=
 protocols work with from then on.<br>
<br>
The textual abstractions are only there for human comfort, ease of configur=
ation, and great flexibility of indirection, but abstractions are just mean=
s to an end. =A0After the address abstractions are de-abstracted, protocols=
 work with the much more efficient binary representations. =A0That&#39;s pr=
actically universal.<br>

<br>
It&#39;s easy to give a practical example of such operation. =A0For example=
, consider a design in which all VW objects have two parts, an in-world obj=
ect (IWO) and an in-client object (ICO), where the ICO is replicated in eac=
h client. =A0Let both parts be active, ie. both sides can be event generato=
rs. =A0It&#39;s easy for ICOs to address update events to their IWO because=
 there is only one IWO, and access could be optimized to network level afte=
r the de-abstraction step for efficiency. =A0But what about updates in the =
reverse direction, which is 1:N?<br>

<br>
In the typical IPv4 environment, the usual approach would be a heavily indi=
rected one, with updates travelling through layer upon layer of middleware =
before reaching their target ICO. =A0In an IPv6 environment in which each I=
CO can have its own IPv6 address, there need be no middleware at all betwee=
n the host kernel and the target object. =A0The resulting increase in effic=
iency by orders of magnitude can have major ramifications on the operation =
of your world and of your clients.<br>

<br>
And the cost of this massive leap in efficiency? =A0Merely to inform the IW=
O of the ICO&#39;s dynamic IPv6 network address, which borders on the trivi=
al.<br>
<br>
One of my main interests is VW scalability, both of worlds and of clients, =
and such efficiency gains are truly important. =A0Scaling VW complexity and=
 rendering of crowds or of highly detailed visualizations requires some lat=
eral thinking and more powerful networking paradigms than we have been used=
 to until now. =A0IPv6 offers some interesting solutions in that direction,=
 and they will be used.<br>

<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
On Thu, May 20, 2010 at 2:43 PM, Richard Barnes &lt;<a href=3D"mailto:rbarn=
es@bbn.com" target=3D"_blank">rbarnes@bbn.com</a>&gt; wrote:<br>
As an aside, there&#39;s nothing that says that subscribers have to be allo=
cated a /64. =A0Some proposed addressing schemes that are more conservative=
 (in the Asia/Pacific region IIRC) actually assign much longer prefixes (sm=
aller address blocks) to customers.<br>

<br>
Fine-grained addressability is not the same as fine-grained allocation of *=
IP* addresses. Think of it this way: HTTP has very fine-grained addressabil=
ity, with individual identifier/locators for pages, images, scripts, etc. =
=A0It&#39;s able to accomplish this not by assigning an IPv6 address to eve=
ry object, but by using an application-layer identifier/locator -- namely a=
 URL.<br>

<br>
Not using IPv6 addresses in applications is not painting oneself into an IP=
v4 corner, it&#39;s good protocol design following the layering model of th=
e Internet. =A0(If we&#39;re using IPv4 addresses for identifiers, we shoul=
dn&#39;t be doing that either!) =A0Abstracting over IP addresses is about f=
reeing the application from having to worry about whether its IPv4 or IPv6 =
or IPv10 or X.25 or whatever else at the network layer.<br>

<br>
--Richard<br>
<br>
<br>
<br>
<br>
On May 20, 2010, at 9:23 AM, Morgaine wrote:<br>
<br>
On Thu, May 20, 2010 at 10:59 AM, Han Sontse &lt;<a href=3D"http://han.sont=
se.sl" target=3D"_blank">han.sontse.sl</a>@<a href=3D"http://gmail.com" tar=
get=3D"_blank">gmail.com</a>&gt; wrote:<br>
I recognize that it is temping to take advantage of the huge address space =
that IPv6 offers but my test engineer instincts tell me it is unwise to do =
so.<br>
<br>
<br>
I too am an engineer, but solid engineering instincts do not tell us to use=
 only those facilities whose numbers or sizes can be tested exhaustively. =
=A0If it were so, we would not have multi-terabyte disk drives today.<br>

<br>
The /64 minimum routable subnet of IPv6 address space was not designed as i=
t was because people were expected to need 2^64 NIC cards in their PCs. =A0=
This immense per-user address block was created because IPv6 designers coul=
d see beyond IPv4&#39;s use of addresses for host interface identification,=
 and were visionary enough to realize that all objects could benefit from n=
etwork addressability. =A0This also happens to be one of the key messages o=
f REST. =A0Addressability is extremely important, the finer the better, not=
 only on the Web, and not only with URIs.<br>

<br>
With IPv6 just around the corner, I foresee such addressability at fine lev=
els of granularity appearing in VWs relatively soon. =A0IPv4 worlds will ha=
ve to emulate what IPv6 worlds achieve natively, and that is the right way =
around. =A0When legacy design restricts progress, the only thing it achieve=
s is rapid obsolescence.<br>

<br>
I would prefer VWRAP not to be painting itself into an IPv4 corner of obsol=
escence before it&#39;s even released, which is why I&#39;m raising this to=
pic --- it&#39;s intended as a heads-up for the group.<br>
<br>
Since the rise of VWs and IPv6 take-up are going to occur concurrently, I t=
hink the next few years are going to be very interesting on the VW networki=
ng front. =A0My recommendation is to observe carefully what happens, and no=
t to make any rash decisions based on legacy ideas that could cut off your =
future.<br>

<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
On Thu, May 20, 2010 at 10:59 AM, Han Sontse &lt;<a href=3D"http://han.sont=
se.sl" target=3D"_blank">han.sontse.sl</a>@<a href=3D"http://gmail.com" tar=
get=3D"_blank">gmail.com</a>&gt; wrote:<br>
It&#39;s a bad idea to use IP addresses for anything other than addressing =
a machine level interface. =A0Using them to interface objects at or above t=
he application level is asking for trouble. =A0 UUIDs are UUIDs... IP addre=
sses are IP addresses. =A0 The two should not be mixed. =A0 I recognize tha=
t it is temping to take advantage of the huge address space that IPv6 offer=
s but my test engineer instincts tell me it is unwise to do so.<br>

<br>
Han.<br>
<br>
On May 20, 2010, at 2:50 AM, Morgaine wrote:<br>
<br>
A /64 is the smallest routable IPv6 subnet, hence there is no extra routing=
 overhead for the 2^(128-64) addresses in the basic block that every user w=
ill have allocated.<br>
<br>
Needless to say, there won&#39;t be anything like 2^64 objects in your scen=
egraph, so if you use your IPv6 address space to address every scenegraph o=
bject that you have instantiated client-side, you will still have an extrem=
ely sparsely used /64 block. =A0You&#39;ll be keeping track of which addres=
ses you have assigned dynamically of course. (An address space of this size=
 is not linearly scannable in realistic time.)<br>

<br>
In principle this is no different to using UUIDs --- your IPv6 micro-server=
s will have unguessable IPv6 addresses within your /64 block, and it&#39;ll=
 be up to you to tell other participants in the protocol (for example serve=
r-side objects) with which of your IPv6 micro-servers they are to communica=
te. =A0This is why an ADT that is supportive of IPv6 operation needs to be =
able to carry such data efficiently --- the UUID is no longer the only 128-=
bit datum of interest.<br>

<br>
Of course your entire /64 block is routed as one, since there are no smalle=
r routable subnets in IPv6, and therefore your objections about routing non=
-scalability do not apply.<br>
<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
On Wed, May 19, 2010 at 10:56 PM, Richard Barnes &lt;<a href=3D"mailto:rbar=
nes@bbn.com" target=3D"_blank">rbarnes@bbn.com</a>&gt; wrote:<br>
The impact of IPv6 on VWs should be far less than you imagine, I think. :)<=
br>
<br>
It has often been said that many, many things will be assigned IPv6 address=
es. =A0There will certainly be enough to go around, but that doesn&#39;t ma=
ke them good application-layer identifiers. =A0If you want to use IP addres=
ses with IP, they have to route, and that means that they have to be either=
 (1) topologically assigned, or (2) overlay routed, e.g., with mobile IP. =
=A0So if you want to use an IP address to address something, you&#39;re goi=
ng to have to either change that address when the thing gets connected diff=
erently, or you&#39;ll need some overlay routing scheme to route to a persi=
stent address. =A0(And if you&#39;re not going to use the address with IP, =
then why would you use an IP address?)<br>

<br>
VWRAP, as an application layer protocol, has a choice about what identifier=
s to use for things and how to use those identifiers. =A0ISTM that using IP=
 addresses (again, of either type) remains a bad idea, compared with someth=
ing that is decoupled from the routing layer.<br>

<br>
As far as the DNS, I&#39;m not sure what your point is:<br>
(i) DNS caching has been around for decades<br>
(ii) DNS names can already refer to multiple addresses<br>
(iii) Depends on implementation. =A0Maybe there&#39;s some application-laye=
r way to resolve names. =A0E.g., SIP endpoints don&#39;t need to have DNS r=
ecords because the INVITE transaction maps from SIP URIs to IP addresses.<b=
r>

(iv) From RFC 4291: &quot;IPv6 addresses are 128-bit identifiers for interf=
aces and sets of<br>
interfaces&quot;<br>
(v) Seems like there&#39;s a use case lurking, hard to address without deta=
ils. =A0But you&#39;re probably still at the application layer. =A0For inst=
ance, if you were telling your peer to send you an HTTP request, you would =
send an HTTP URI, which can already handle IPv6 addresses.<br>

<br>
--Richard<br>
<br>
<br>
<br>
On May 19, 2010, at 9:35 AM, Morgaine wrote:<br>
<br>
The impact of IPv6 on VWs is going to be far greater than you imagine, I be=
lieve. =A0As things stand, VWRAP is being designed around the features and =
limitations of IPv4 networking. =A0It will of course be able to ride on top=
 of IPv6 as a transport, but unable to benefit from its improved feature se=
t, unless we provide the means to do so.<br>

<br>
The question &quot;Why is there ever a need to carry an IP address in this =
application-layer protocol, as opposed to, say, a DNS name or a URI?&quot; =
suggests an IPv4 mindset, because in IPv6 it has a variety of possible answ=
ers: =A0(i) When the DNS lookup has already been done and does not need to =
be done again, (ii) When a FQDN maps to multiple addresses, but you want to=
 refer to a specific one, (iii) When an IPv6 address does not have an exter=
nal address record, (iv) When the host is already known and the IP address =
denotes something other than a physical NIC interface, or (v) When listener=
s are allocated locally and dynamically for the current session only, and t=
heir IP addresses need to be communicated to a peer --- this will be an ext=
remely common use case with IPv6.<br>

<br>
In today&#39;s IPv4-based systems, it is normal for a user&#39;s machine to=
 have a single IP address, and for a client on that machine to talk to a se=
rver that has a single customer-facing IP address too (although it may also=
 have others that are not public). =A0In IPv6-based systems, this simple sc=
enario is still possible but represents only a special case among a new and=
 vastly expanded set of IPv6 use cases.<br>

<br>
The smallest allocatable block of IPv6 address space is a /64, so 2^(128-64=
) IP addresses is the number that most normal IPv6 users will have, althoug=
h the much larger /48 blocks of 2^80 addresses are commonly assigned to use=
rs as well. =A0With such IP riches client-side, it is certain that they wil=
l be used for something, and the obvious suggestion is to give every VW obj=
ect an IPv6 address of its own.<br>

<br>
Lest we forget, one of the most important properties of the REST paradigm i=
s addressability, but the benefits of high addressability go far beyond the=
 Web. =A0This is a property that will become ubiquitous throughout networke=
d computing with IPv6. =A0It&#39;s probably no exaggeration to say that *ev=
erything* will be getting its own IP address. :-)<br>

<br>
Faced with that future, it&#39;s a mistake to think in IPv4 terms and consi=
der IPv6 addresses as merely denoting a host which can be obtained from its=
 FQDN. =A0That&#39;s IPv4 thinking, and represents only a very basic use ca=
se for IPv6. =A0In more extended use cases, IPv6 addresses will become much=
 more like active local UUIDs than like today&#39;s host IP addresses. =A0T=
hey will be used for inner-application addressing, for example to make ever=
y object in an application an addressable micro-server.<br>

<br>
VWRAP is being born into an IPv6 world, and it would be a mistake to hardwi=
re IPv4 thinking into its design. =A0We continually refer to the need for e=
xtensibility and a desire to future-proof the protocol, but lip service is =
not enough. =A0Adding IPv6 addresses to the underlying ADT would provide a =
bare minimum level of thinking ahead to support VWRAP implementations that =
embrace large numbers of communicating objects. =A0(A generally extensible =
ADT would of course achieve the same thing, and more.)<br>

<br>
<br>
Morgaine.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
On Mon, May 17, 2010 at 3:50 PM, David W Levine &lt;<a href=3D"mailto:dwl@u=
s.ibm.com" target=3D"_blank">dwl@us.ibm.com</a>&gt; wrote:<br>
<br>
<br>
<a href=3D"mailto:vwrap-bounces@ietf.org" target=3D"_blank">vwrap-bounces@i=
etf.org</a> wrote on 05/17/2010 10:08:26 AM:<br>
<br>
&gt; [image removed]<br>
&gt;<br>
&gt; Re: [vwrap] VWRAP and IPv6<br>
&gt;<br>
&gt; Richard Barnes<br>
&gt;<br>
&gt; to:<br>
&gt;<br>
&gt; Morgaine<br>
&gt;<br>
&gt; 05/17/2010 10:09 AM<br>
&gt;<br>
&gt; Sent by:<br>
&gt;<br>
&gt; <a href=3D"mailto:vwrap-bounces@ietf.org" target=3D"_blank">vwrap-boun=
ces@ietf.org</a><br>
&gt;<br>
&gt; Cc:<br>
&gt;<br>
&gt; vwrap<br>
&gt;<br>
&gt; In the spirit of good layering, it seems like we should be talking<br>
&gt; about avoiding direct reliance on IP addresses instead of how we can<b=
r>
&gt; accommodate different addresses in the protocol. =A0Why is there ever =
a<br>
&gt; need to carry an IP address in this application-layer protocol, as<br>
&gt; opposed to, say, a DNS name or a URI?<br>
&gt;<br>
&gt; --Richard<br>
&gt;<br>
+1<br>
<br>
We may from time to time have a IP address stuck in the form of a URI<br>
which has the dotted decimal form of an resource. The spec should make<br>
sure that form can be an IPV6 address, but that should be very straight<br>
forward.<br>
<br>
There may be some IPV6 features which eventually impact us at the protocol<=
br>
design level, but the entire VWRAP specification has been written in terms =
of<br>
URIs and Capabilities, not in terms of low level IP addresses. It would tak=
e an<br>
incredibly powerful argument to suggest that this should change. Likewise, =
while<br>
IPV6 changes addressing at the bottom of the stack, it doesn&#39;t apprecia=
bly change<br>
the cost of holding open sessions, of managing sockets and buffers inside o=
f<br>
clients (especially lightweight devices) Further while we can all devoutly =
hope<br>
that IPV6 finally deploys broadly, making it a dependancy in the near term =
feels<br>
rather like a roadblock to possible adoption.<br>
<br>
- David<br>
~ Zha<br>
<br>
<br>
<br>
&gt;<br>
&gt; On May 14, 2010, at 7:32 AM, Morgaine wrote:<br>
&gt;<br>
&gt; &gt; Despite exceedingly low takeup of IPv6 so far, it&#39;s coming, a=
nd in<br>
&gt; &gt; the context of IETF WG rates of progress, it is really imminent. =
=A0Of<br>
&gt; &gt; special relevance to us is that IPv4 addresses are projected to r=
un<br>
&gt; &gt; out within roughly the same time frame as VWRAP materializes.<br>
&gt; &gt;<br>
&gt; &gt; There is little point in creating a new VW protocol today purely =
in<br>
&gt; &gt; the context of IPv4 without thinking about tomorrow&#39;s IPv6<br=
>
&gt; &gt; environment. =A0By the time that VWRAP is fully defined, we shoul=
d<br>
&gt; &gt; expect a substantial and rapidly increasing proportion of VWRAP<b=
r>
&gt; &gt; implementations to occur in IPv6-accessible worlds. =A0This is a<=
br>
&gt; &gt; situation for which we need to plan now, otherwise the protocol w=
ill<br>
&gt; &gt; be obsolete before it&#39;s even ready.<br>
&gt; &gt;<br>
&gt; &gt; To get the ball rolling, here are a few IPv6-related issues that =
we<br>
&gt; &gt; could usefully address in the group:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0=95 The 128-bit IP address of IPv6 is likely to become a c=
ommon<br>
&gt; &gt; payload, so it should be supported natively. =A0LLSD already supp=
orts<br>
&gt; &gt; one 128-bit data type of course, the UUID. =A0IPv6 addresses shou=
ld<br>
&gt; &gt; not be transported in UUID fields however, since their statistica=
l<br>
&gt; &gt; properties and semantics are totally different. =A0In any case, t=
he<br>
&gt; &gt; two spaces are disjoint so confusing them would be a mistake. =A0=
The<br>
&gt; &gt; IPv6 address seems a good candidate for its own defined type, in =
the<br>
&gt; &gt; absence of wide integers.<br>
&gt; &gt; =A0 =A0=95 The extremely large address space of IPv6 has often be=
en<br>
&gt; &gt; portrayed as allowing everything around us to have its own IP<br>
&gt; &gt; address. =A0In the context of virtual worlds, this idea can actua=
lly<br>
&gt; &gt; be put to good use, with each virtual object bearing its own IPv6=
<br>
&gt; &gt; address. =A0One candidate application for this has already been<b=
r>
&gt; &gt; described in earlier discussions --- for example, implementing<br=
>
&gt; &gt; virtual object simulation in two parts, one client-side and one<b=
r>
&gt; &gt; world-side, the two parts communicating directly. =A0IPv6 address=
ing<br>
&gt; &gt; of objects makes this relatively easy to achieve efficiently, so =
its<br>
&gt; &gt; implementation in IPv6-based worlds is almost inevitable before<b=
r>
&gt; &gt; long. =A0VWRAP should be ready for this.<br>
&gt; &gt; =A0 =A0=95 The event queue in current implementations provides an=
 indirect<br>
&gt; &gt; and highly inefficient way of achieving world-to-client<br>
&gt; &gt; communications. =A0IPv6 offers opportunities for direct communica=
tion<br>
&gt; &gt; that can make the event queue approach obsolete, so it&#39;s wort=
h<br>
&gt; &gt; examining IPv6-oriented alternatives.<br>
&gt; &gt; =A0 =A0=95 We recently discussed feature and protocol negotiation=
 within<br>
&gt; &gt; VWRAP. =A0IPv6 provides much opportunity for new features and pro=
tocol<br>
&gt; &gt; pathways to be negotiated between endpoints, so it gives us a ver=
y<br>
&gt; &gt; real and imminent set of use cases for negotiation.<br>
&gt; &gt;<br>
&gt; &gt; It would also be a feather in VWRAP&#39;s cap to be considered an=
 &quot;IPv6-<br>
&gt; &gt; capable application protocol&quot; in a stronger sense than just =
to be<br>
&gt; &gt; carried by IPv6 networks. =A0IPv6 does after all bring new abilit=
ies<br>
&gt; &gt; to the table, such as the huge addressing, and it would be a mist=
ake<br>
&gt; &gt; to ignore them.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Morgaine.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; vwrap mailing list<br>
&gt; &gt; <a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.or=
g</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D=
"_blank">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; vwrap mailing list<br>
&gt; <a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
<br>
<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org" target=3D"_blank">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
</blockquote>
<br>
</div></div></blockquote></div><br>

--0016e6497e96b1a9430487091a65--

From barryleiba.mailing.lists@gmail.com  Wed May 26 18:14:39 2010
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 616C13A67A5 for <vwrap@core3.amsl.com>; Wed, 26 May 2010 18:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_50=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 BkufZMqcDieK for <vwrap@core3.amsl.com>; Wed, 26 May 2010 18:14:38 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 88E833A6A15 for <vwrap@ietf.org>; Wed, 26 May 2010 18:14:36 -0700 (PDT)
Received: by fxm14 with SMTP id 14so353416fxm.31 for <vwrap@ietf.org>; Wed, 26 May 2010 18:14:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to:date :message-id:subject:from:to:content-type; bh=cDpVhishL402Q+mOoo37fYZ0GLB6Fzl/f694NioKceU=; b=QWiKmxL5VbxpKU0KmUCMFIcSOSOWz8Q7Qnk/r6igf3z+IkP3IevjCEVMhtTbYh4P6W SUTjkJNQm9phTmDtclXy7Fm9fXKjped0q5myWUOiD8wNHgMqgLgzolMmvoyncLe3WHrf W1VdyrjCscEWK2Dp0DPAtFDs//PtUKQ6R0C98=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; b=OQ6JeI2WT3WLe4rkf6tmgCv5sJFsTq7hTM+/+AM2LByhkhmaikoglm7OYItOU8E4A+ rZjEXM9Cy+TTiSwCpCxkjarqhCc2BYjbaKBZTmlymTbc8TDAMZKxfhVTIMxTLtH14geT JFuxZYQz53tcHpLfJoY6pAZjySKLkzAo0wuQc=
MIME-Version: 1.0
Received: by 10.223.58.83 with SMTP id f19mr8373819fah.88.1274922863316; Wed,  26 May 2010 18:14:23 -0700 (PDT)
Received: by 10.223.122.141 with HTTP; Wed, 26 May 2010 18:14:23 -0700 (PDT)
Date: Wed, 26 May 2010 21:14:23 -0400
Message-ID: <AANLkTin1VUFz26_196KCclBEEL3TJMpjb8H_hLY0T9Pv@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: vwrap@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [vwrap] Moving startup documents into the working group
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: barryleiba@computer.org
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2010 01:14:39 -0000

It's time to think about which pre-WG documents the working group is
ready to adopt.  As I introduce this, I want to stress that adoption
of documents does NOT mean that the group has consensus on the current
content of those documents, that it collectively agrees with what they
say, that the documents are in any sense "ready".  All it means is
that the working group thinks they're headed in the right direction,
and can be used as a starting point for further refinement.  Indeed,
documents adopted as starting points by the working group might have a
number of significant revisions before they are declared "ready" and
are sent to the IESG.

That said, the chairs would like to take a poll on whether the
following are ready for adoption on their next revisions:

* Introduction and Goals
http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01

* Trust Model and User Authentication
http://tools.ietf.org/html/draft-hamrick-vwrap-authentication-01

* Abstract Type System for the Transmission of Dynamic Structured Data
http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00

* Client Application Launch Message
http://tools.ietf.org/html/draft-hamrick-vwrap-launch-00

* Foundation
http://tools.ietf.org/html/draft-lentczner-vwrap-foundation-00


Please reply in this thread as in this example, listing each document
and giving your opinion:
> Introduction and Goals - yes
> Trust Model and User Authentication - yes
> Abstract Type System - yes
> Client Application Launch Message - yes
> Foundation - yes

Please make your opinion either "yes" (the working group should adopt
the document) or "no" (the working group should not adopt the
document).

Please do not discuss anything else in this thread.  If you need to
discuss your answer, please start a new thread, with a new subject
line, for the discussion.  If you have any issues you prefer to bring
to the chairs off-list, contact us at <vwrap-chairs@tools.ietf.org>.

Thanks very much.

-- Barry, as chair

From kmancuso@gmail.com  Thu May 27 12:35:58 2010
Return-Path: <kmancuso@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E1D33A6D97 for <vwrap@core3.amsl.com>; Thu, 27 May 2010 12:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 k1rytGQpRj2h for <vwrap@core3.amsl.com>; Thu, 27 May 2010 12:35:54 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id E1D2D3A6F5A for <vwrap@ietf.org>; Thu, 27 May 2010 12:30:34 -0700 (PDT)
Received: by wye20 with SMTP id 20so270149wye.31 for <vwrap@ietf.org>; Thu, 27 May 2010 12:29:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:received :reply-to:date:message-id:subject:from:to:content-type; bh=FIr3sUXBTqHauiwZfZ2p87tfxEUFGrIj3l/Nuxbl1dw=; b=djKtZRZpRZUqoPEFl/DGqQg2LNQH2SI18bEKMrPci7hcYIOY5jGVV8SCCyC+rIjX3R isnvF691GlifsDPj2vnVvND6smx8H3UL/hzNizL1CPCHreoWXUxfa3je+6TCsP8A0a53 /RLFkqXiatWOS11r51ZE2f5u+uspASQA8aFq0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; b=Ozr8da193XFdo9ZN38A9Xzg8oG2d3NxvRP113AE8RuruJwbQRoNAuDNcctBiazyscN 52/TJ1SDX5gpw1MHg+MTEgql9hRWo+htPNNqI3dASNA7Z25/GwMMa7hnmRkZUrPt8jNr VimqANk27dgdaXAeeeWQjub7a6pag9cG3QB2g=
MIME-Version: 1.0
Received: by 10.216.85.146 with SMTP id u18mr142622wee.111.1274988591843; Thu,  27 May 2010 12:29:51 -0700 (PDT)
Received: by 10.216.48.2 with HTTP; Thu, 27 May 2010 12:29:51 -0700 (PDT)
Received: by 10.216.48.2 with HTTP; Thu, 27 May 2010 12:29:51 -0700 (PDT)
Date: Thu, 27 May 2010 12:29:51 -0700
Message-ID: <AANLkTik4WcF2nkSPQ-rWt-8AlinxQuMYB8Qv8CXWV0Ys@mail.gmail.com>
From: Katherine Mancuso <kmancuso@gmail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d9a0f01c08bf0487986aae
Subject: [vwrap] Moving startup documents into the working group
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: kmancuso@gmail.com
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2010 19:35:58 -0000

--0016e6d9a0f01c08bf0487986aae
Content-Type: text/plain; charset=ISO-8859-1

I am unequipped to vote on the more technical documents, but

Intro - yes
Foundations - no

(I'm not sure how votes are interpreted, so: I'm stating with this vote that
foundations doesn't yet have enough clarity & precision for me to say with
confidence it's headed in the right direction.)

-katherine/muse

--0016e6d9a0f01c08bf0487986aae
Content-Type: text/html; charset=ISO-8859-1

<p>I am unequipped to vote on the more technical documents, but</p>
<p>Intro - yes<br>
Foundations - no</p>
<p>(I&#39;m not sure how votes are interpreted, so: I&#39;m stating with this vote that foundations doesn&#39;t yet have enough clarity &amp; precision for me to say with confidence it&#39;s headed in the right direction.)</p>

<p>-katherine/muse</p>

--0016e6d9a0f01c08bf0487986aae--

From morgaine.dinova@googlemail.com  Fri May 28 07:43:39 2010
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E8233A684E for <vwrap@core3.amsl.com>; Fri, 28 May 2010 07:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.624
X-Spam-Level: 
X-Spam-Status: No, score=0.624 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 McNFwAkXp17r for <vwrap@core3.amsl.com>; Fri, 28 May 2010 07:43:38 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id A12523A6828 for <vwrap@ietf.org>; Fri, 28 May 2010 07:43:37 -0700 (PDT)
Received: by wye20 with SMTP id 20so932456wye.31 for <vwrap@ietf.org>; Fri, 28 May 2010 07:43:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=2spss138SE9wPQaYyaZXrr441fDkK+95LI76D8ZaQ0Q=; b=GWr6lpJmGVU2UzjyAibvJcukam6HYb71KJNdJ3S2vy9qp+IvL8HAQkiDxU1FZmeBB4 7AuR2XMDll+pT4JXjInm4sx1KIiBGq4tfSGOCC6UX7U9QQQmPc3tIAl2Vo5ooyJ8W2Ew xqHeuOjAiUhZ31pD/32YXIHtVcSCTKc1st0Os=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=BHl95v1GMRXnRS/Cddj6MgziXD6sDSG1SLxUbrjXMCT49StA9PudVurSidyE8b7o5p 7bqH5NuwMf/aXpWtA48ux+hEZhHYw//L7SKKVi+ymMDx+5GW21/9nYoipedcHha3b/Ka IygS4cjFxWFThlwnHUjnJqmdgyc6PvDqv7eVI=
MIME-Version: 1.0
Received: by 10.216.88.132 with SMTP id a4mr1683941wef.16.1275057804211; Fri,  28 May 2010 07:43:24 -0700 (PDT)
Received: by 10.216.26.132 with HTTP; Fri, 28 May 2010 07:43:24 -0700 (PDT)
In-Reply-To: <AANLkTin1VUFz26_196KCclBEEL3TJMpjb8H_hLY0T9Pv@mail.gmail.com>
References: <AANLkTin1VUFz26_196KCclBEEL3TJMpjb8H_hLY0T9Pv@mail.gmail.com>
Date: Fri, 28 May 2010 15:43:24 +0100
Message-ID: <AANLkTilJSf_cz-gpU_ZkE7_sRs2OjLpe87ZqinuIM8xo@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d975aa7cf9360487a8877a
Subject: Re: [vwrap] Moving startup documents into the working group
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2010 14:43:39 -0000

--0016e6d975aa7cf9360487a8877a
Content-Type: text/plain; charset=ISO-8859-1

My Yes/No responses (discussion to follow in a different thread):

> Introduction and Goals - yes
> Trust Model and User Authentication - yes
> Abstract Type System - yes
> Client Application Launch Message - no
> Foundation - no


Morgaine.





============================================

On Thu, May 27, 2010 at 2:14 AM, Barry Leiba <
barryleiba.mailing.lists@gmail.com> wrote:

> It's time to think about which pre-WG documents the working group is
> ready to adopt.  As I introduce this, I want to stress that adoption
> of documents does NOT mean that the group has consensus on the current
> content of those documents, that it collectively agrees with what they
> say, that the documents are in any sense "ready".  All it means is
> that the working group thinks they're headed in the right direction,
> and can be used as a starting point for further refinement.  Indeed,
> documents adopted as starting points by the working group might have a
> number of significant revisions before they are declared "ready" and
> are sent to the IESG.
>
> That said, the chairs would like to take a poll on whether the
> following are ready for adoption on their next revisions:
>
> * Introduction and Goals
> http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01
>
> * Trust Model and User Authentication
> http://tools.ietf.org/html/draft-hamrick-vwrap-authentication-01
>
> * Abstract Type System for the Transmission of Dynamic Structured Data
> http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00
>
> * Client Application Launch Message
> http://tools.ietf.org/html/draft-hamrick-vwrap-launch-00
>
> * Foundation
> http://tools.ietf.org/html/draft-lentczner-vwrap-foundation-00
>
>
> Please reply in this thread as in this example, listing each document
> and giving your opinion:
> > Introduction and Goals - yes
> > Trust Model and User Authentication - yes
> > Abstract Type System - yes
> > Client Application Launch Message - yes
> > Foundation - yes
>
> Please make your opinion either "yes" (the working group should adopt
> the document) or "no" (the working group should not adopt the
> document).
>
> Please do not discuss anything else in this thread.  If you need to
> discuss your answer, please start a new thread, with a new subject
> line, for the discussion.  If you have any issues you prefer to bring
> to the chairs off-list, contact us at <vwrap-chairs@tools.ietf.org>.
>
> Thanks very much.
>
> -- Barry, as chair
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>

--0016e6d975aa7cf9360487a8877a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

My Yes/No responses (discussion to follow in a different thread):<br><br>&g=
t; Introduction and Goals - yes<br>
&gt; Trust Model and User Authentication - yes<br>
&gt; Abstract Type System - yes<br>
&gt; Client Application Launch Message - no<br>
&gt; Foundation - no<br><br><br>Morgaine.<br><br><br><br><br><br>=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><br><div class=3D"gmail=
_quote">On Thu, May 27, 2010 at 2:14 AM, Barry Leiba <span dir=3D"ltr">&lt;=
<a href=3D"mailto:barryleiba.mailing.lists@gmail.com">barryleiba.mailing.li=
sts@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It&#39;s time to =
think about which pre-WG documents the working group is<br>
ready to adopt. =A0As I introduce this, I want to stress that adoption<br>
of documents does NOT mean that the group has consensus on the current<br>
content of those documents, that it collectively agrees with what they<br>
say, that the documents are in any sense &quot;ready&quot;. =A0All it means=
 is<br>
that the working group thinks they&#39;re headed in the right direction,<br=
>
and can be used as a starting point for further refinement. =A0Indeed,<br>
documents adopted as starting points by the working group might have a<br>
number of significant revisions before they are declared &quot;ready&quot; =
and<br>
are sent to the IESG.<br>
<br>
That said, the chairs would like to take a poll on whether the<br>
following are ready for adoption on their next revisions:<br>
<br>
* Introduction and Goals<br>
<a href=3D"http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01" target=
=3D"_blank">http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01</a><br>
<br>
* Trust Model and User Authentication<br>
<a href=3D"http://tools.ietf.org/html/draft-hamrick-vwrap-authentication-01=
" target=3D"_blank">http://tools.ietf.org/html/draft-hamrick-vwrap-authenti=
cation-01</a><br>
<br>
* Abstract Type System for the Transmission of Dynamic Structured Data<br>
<a href=3D"http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00" t=
arget=3D"_blank">http://tools.ietf.org/html/draft-hamrick-vwrap-type-system=
-00</a><br>
<br>
* Client Application Launch Message<br>
<a href=3D"http://tools.ietf.org/html/draft-hamrick-vwrap-launch-00" target=
=3D"_blank">http://tools.ietf.org/html/draft-hamrick-vwrap-launch-00</a><br=
>
<br>
* Foundation<br>
<a href=3D"http://tools.ietf.org/html/draft-lentczner-vwrap-foundation-00" =
target=3D"_blank">http://tools.ietf.org/html/draft-lentczner-vwrap-foundati=
on-00</a><br>
<br>
<br>
Please reply in this thread as in this example, listing each document<br>
and giving your opinion:<br>
&gt; Introduction and Goals - yes<br>
&gt; Trust Model and User Authentication - yes<br>
&gt; Abstract Type System - yes<br>
&gt; Client Application Launch Message - yes<br>
&gt; Foundation - yes<br>
<br>
Please make your opinion either &quot;yes&quot; (the working group should a=
dopt<br>
the document) or &quot;no&quot; (the working group should not adopt the<br>
document).<br>
<br>
Please do not discuss anything else in this thread. =A0If you need to<br>
discuss your answer, please start a new thread, with a new subject<br>
line, for the discussion. =A0If you have any issues you prefer to bring<br>
to the chairs off-list, contact us at &lt;<a href=3D"mailto:vwrap-chairs@to=
ols.ietf.org">vwrap-chairs@tools.ietf.org</a>&gt;.<br>
<br>
Thanks very much.<br>
<br>
-- Barry, as chair<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
</blockquote></div><br>

--0016e6d975aa7cf9360487a8877a--

From morgaine.dinova@googlemail.com  Fri May 28 08:00:19 2010
Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29AA63A6A4A for <vwrap@core3.amsl.com>; Fri, 28 May 2010 08:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.624
X-Spam-Level: 
X-Spam-Status: No, score=0.624 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 4nc4b6025YGh for <vwrap@core3.amsl.com>; Fri, 28 May 2010 08:00:13 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 0B4BE3A6A45 for <vwrap@ietf.org>; Fri, 28 May 2010 08:00:12 -0700 (PDT)
Received: by wye20 with SMTP id 20so947421wye.31 for <vwrap@ietf.org>; Fri, 28 May 2010 08:00:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=PNJ/YFYkHrjZXR6B6s3rs9b1mcihOMojk6M33z3YKP8=; b=gMoVUZRad8212U3ZooAGZXfZl36REXIm1Vl7jnQpt9k9lJuUYYaDnEuiobn1w3Hzwa T/dJw6HLmpjvvAisskPgWHUjthBNaYksEKW77rB8Gm+Bo0hbo3v4V5ckXvnCNwJCcY2s kbaIlXjbsPDiIs3MGkVpwavS47Az0SNwSiPug=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=fCAQ8LO3KoTudN9lqiDNiV5ubiw1lrO2Ad8PDX7216E6qjh2oCd2TTVo46gdUBC8us ObYesHmrvdt4V8AToCB9B6fD+PfpP8m35kR78QvI64BIq3L8LOE7zMkRVTV8qvNM//vY 0BFW+/zzZey9J6WsYOhYJs/jZtx+IgtTpxj78=
MIME-Version: 1.0
Received: by 10.216.90.13 with SMTP id d13mr1697828wef.18.1275058324377; Fri,  28 May 2010 07:52:04 -0700 (PDT)
Received: by 10.216.26.132 with HTTP; Fri, 28 May 2010 07:52:04 -0700 (PDT)
In-Reply-To: <AANLkTin1VUFz26_196KCclBEEL3TJMpjb8H_hLY0T9Pv@mail.gmail.com>
References: <AANLkTin1VUFz26_196KCclBEEL3TJMpjb8H_hLY0T9Pv@mail.gmail.com>
Date: Fri, 28 May 2010 15:52:04 +0100
Message-ID: <AANLkTim6Z40qjorf7L8SyiofmgJdaoNv3voV5hobY6nE@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary=0016e6d7dff57e0fde0487a8a69d
Subject: Re: [vwrap] [DISCUSSION] Moving startup documents into the working group
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2010 15:00:19 -0000

--0016e6d7dff57e0fde0487a8a69d
Content-Type: text/plain; charset=ISO-8859-1

This is a new discussion thread with a new subject line, as Barry requested.

I gave three documents a Yes and two a No, the meaning of "Yes" being as
Barry said, that they represent a viable starting point --- many large
changes (to some) will be needed before the "Yes" drafts are anywhere near
to being correct and useful though:

> Introduction and Goals - yes
> Trust Model and User Authentication - yes
> Abstract Type System - yes

Now regarding my two "No" responses, meaning "not adequate for group
consideration":

> Client Application Launch Message - no
> Foundation - no

"*Client Application Launch Message*" -- this simply has no business being
part of the VWRAP protocol suite at all.  Launching applications is
completely outside of our remit I believe, and undoubtedly there will be a
large number of ways of achieving it, depending on the platform.  The
closest I think we might get to this area is to define the meaning of a
"landmark" entity (as an URI in the protocol), but blessing one particular
use of such an entity is quite unnecessary.

"*Foundation*" --- I gave this a "No" because it appears to be an
"archeological OGP" document, unearthed from the original days of OGP.  It
does not reflect the OGPX or VWRAP group discussions at all, and is even
oblivious of the group charter --- notice its attempt to create a single
"vast, Internet wide virtual world".

What's more, we already have a foundational document --- it's called
"Introduction and Goals".  Admittedly it's not a very friendly document
either as background reading nor for the implementer, but nevertheless its
purpose was to provide the foundation, I believe.  Perhaps the new
"Foundation" document was a gentle attempt at saying "Unreadable" to the
first document, and asking for a refactoring?  If so then I'd support that,
because currently "Introduction and Goals" is a meandering document with
little clarity of purpose.  Perhaps "Introduction and Goals" should be
renamed "Protocol Elements" and have all its background sections removed,
which would then leave room for an "Introduction" document that would
provide background and glue for everything else, but no details.

I get the feeling that a big refactoring is due.  Documents have been
appearing out of the blue without any prior discussion of their need or of
their scope, as a result of which we currently have a random checkerboard of
documents, and nothing outside of the type system is particularly well
described or useful so far.


Morgaine.





=========================================

On Thu, May 27, 2010 at 2:14 AM, Barry Leiba <
barryleiba.mailing.lists@gmail.com> wrote:

> It's time to think about which pre-WG documents the working group is
> ready to adopt.  As I introduce this, I want to stress that adoption
> of documents does NOT mean that the group has consensus on the current
> content of those documents, that it collectively agrees with what they
> say, that the documents are in any sense "ready".  All it means is
> that the working group thinks they're headed in the right direction,
> and can be used as a starting point for further refinement.  Indeed,
> documents adopted as starting points by the working group might have a
> number of significant revisions before they are declared "ready" and
> are sent to the IESG.
>
> That said, the chairs would like to take a poll on whether the
> following are ready for adoption on their next revisions:
>
> * Introduction and Goals
> http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01
>
> * Trust Model and User Authentication
> http://tools.ietf.org/html/draft-hamrick-vwrap-authentication-01
>
> * Abstract Type System for the Transmission of Dynamic Structured Data
> http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00
>
> * Client Application Launch Message
> http://tools.ietf.org/html/draft-hamrick-vwrap-launch-00
>
> * Foundation
> http://tools.ietf.org/html/draft-lentczner-vwrap-foundation-00
>
>
> Please reply in this thread as in this example, listing each document
> and giving your opinion:
> > Introduction and Goals - yes
> > Trust Model and User Authentication - yes
> > Abstract Type System - yes
> > Client Application Launch Message - yes
> > Foundation - yes
>
> Please make your opinion either "yes" (the working group should adopt
> the document) or "no" (the working group should not adopt the
> document).
>
> Please do not discuss anything else in this thread.  If you need to
> discuss your answer, please start a new thread, with a new subject
> line, for the discussion.  If you have any issues you prefer to bring
> to the chairs off-list, contact us at <vwrap-chairs@tools.ietf.org>.
>
> Thanks very much.
>
> -- Barry, as chair
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>

--0016e6d7dff57e0fde0487a8a69d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

This is a new discussion thread with a new subject line, as Barry requested=
.<br><br>I gave three documents a Yes and two a No, the meaning of &quot;Ye=
s&quot; being as Barry said, that they represent a viable starting point --=
- many large changes (to some) will be needed before the &quot;Yes&quot; dr=
afts are anywhere near to being correct and useful though:<br>
<br>&gt; Introduction and Goals - yes<br>
&gt; Trust Model and User Authentication - yes<br>
&gt; Abstract Type System - yes<br><br>Now regarding my two &quot;No&quot; =
responses, meaning &quot;not adequate for group consideration&quot;:<br><br=
>&gt; Client Application Launch Message - no<br>
&gt; Foundation - no<br><br>&quot;<b>Client Application Launch Message</b>&=
quot; -- this simply has no business being part of the VWRAP protocol suite=
 at all.=A0 Launching applications is completely outside of our remit I bel=
ieve, and undoubtedly there will be a large number of ways of achieving it,=
 depending on the platform.=A0 The closest I think we might get to this are=
a is to define the meaning of a &quot;landmark&quot; entity (as an URI in t=
he protocol), but blessing one particular use of such an entity is quite un=
necessary.<br>
<br>&quot;<b>Foundation</b>&quot; --- I gave this a &quot;No&quot; because =
it appears to be an &quot;archeological OGP&quot; document, unearthed from =
the original days of OGP.=A0 It does not reflect the OGPX or VWRAP group di=
scussions at all, and is even oblivious of the group charter --- notice its=
 attempt to create a single &quot;vast, Internet wide virtual world&quot;.<=
br>
<br>What&#39;s more, we already have a foundational document --- it&#39;s c=
alled &quot;Introduction and Goals&quot;.=A0 Admittedly it&#39;s not a very=
 friendly document either as background reading nor for the implementer, bu=
t nevertheless its purpose was to provide the foundation, I believe.=A0 Per=
haps the new &quot;Foundation&quot; document was a gentle attempt at saying=
 &quot;Unreadable&quot; to the first document, and asking for a refactoring=
?=A0 If so then I&#39;d support that, because currently &quot;Introduction =
and Goals&quot; is a meandering document with little clarity of purpose.=A0=
 Perhaps &quot;Introduction and Goals&quot; should be renamed &quot;Protoco=
l Elements&quot; and have all its background sections removed, which would =
then leave room for an &quot;Introduction&quot; document that would provide=
 background and glue for everything else, but no details.<br>
<br>I get the feeling that a big refactoring is due.=A0 Documents have been=
 appearing out of the blue without any prior discussion of their need or of=
 their scope, as a result of which we currently have a random checkerboard =
of documents, and nothing outside of the type system is particularly well d=
escribed or useful so far.<br>
<br><br>Morgaine.<br><br><br><br><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br><br><div class=3D"gmail_quote">On Thu, May 27, 2010 at 2=
:14 AM, Barry Leiba <span dir=3D"ltr">&lt;<a href=3D"mailto:barryleiba.mail=
ing.lists@gmail.com">barryleiba.mailing.lists@gmail.com</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It&#39;s time to =
think about which pre-WG documents the working group is<br>
ready to adopt. =A0As I introduce this, I want to stress that adoption<br>
of documents does NOT mean that the group has consensus on the current<br>
content of those documents, that it collectively agrees with what they<br>
say, that the documents are in any sense &quot;ready&quot;. =A0All it means=
 is<br>
that the working group thinks they&#39;re headed in the right direction,<br=
>
and can be used as a starting point for further refinement. =A0Indeed,<br>
documents adopted as starting points by the working group might have a<br>
number of significant revisions before they are declared &quot;ready&quot; =
and<br>
are sent to the IESG.<br>
<br>
That said, the chairs would like to take a poll on whether the<br>
following are ready for adoption on their next revisions:<br>
<br>
* Introduction and Goals<br>
<a href=3D"http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01" target=
=3D"_blank">http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01</a><br>
<br>
* Trust Model and User Authentication<br>
<a href=3D"http://tools.ietf.org/html/draft-hamrick-vwrap-authentication-01=
" target=3D"_blank">http://tools.ietf.org/html/draft-hamrick-vwrap-authenti=
cation-01</a><br>
<br>
* Abstract Type System for the Transmission of Dynamic Structured Data<br>
<a href=3D"http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00" t=
arget=3D"_blank">http://tools.ietf.org/html/draft-hamrick-vwrap-type-system=
-00</a><br>
<br>
* Client Application Launch Message<br>
<a href=3D"http://tools.ietf.org/html/draft-hamrick-vwrap-launch-00" target=
=3D"_blank">http://tools.ietf.org/html/draft-hamrick-vwrap-launch-00</a><br=
>
<br>
* Foundation<br>
<a href=3D"http://tools.ietf.org/html/draft-lentczner-vwrap-foundation-00" =
target=3D"_blank">http://tools.ietf.org/html/draft-lentczner-vwrap-foundati=
on-00</a><br>
<br>
<br>
Please reply in this thread as in this example, listing each document<br>
and giving your opinion:<br>
&gt; Introduction and Goals - yes<br>
&gt; Trust Model and User Authentication - yes<br>
&gt; Abstract Type System - yes<br>
&gt; Client Application Launch Message - yes<br>
&gt; Foundation - yes<br>
<br>
Please make your opinion either &quot;yes&quot; (the working group should a=
dopt<br>
the document) or &quot;no&quot; (the working group should not adopt the<br>
document).<br>
<br>
Please do not discuss anything else in this thread. =A0If you need to<br>
discuss your answer, please start a new thread, with a new subject<br>
line, for the discussion. =A0If you have any issues you prefer to bring<br>
to the chairs off-list, contact us at &lt;<a href=3D"mailto:vwrap-chairs@to=
ols.ietf.org">vwrap-chairs@tools.ietf.org</a>&gt;.<br>
<br>
Thanks very much.<br>
<br>
-- Barry, as chair<br>
_______________________________________________<br>
vwrap mailing list<br>
<a href=3D"mailto:vwrap@ietf.org">vwrap@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/vwrap" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/vwrap</a><br>
</blockquote></div><br>

--0016e6d7dff57e0fde0487a8a69d--

From john.hurliman@intel.com  Fri May 28 09:38:42 2010
Return-Path: <john.hurliman@intel.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 67B5C3A69A6 for <vwrap@core3.amsl.com>; Fri, 28 May 2010 09:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.185
X-Spam-Level: 
X-Spam-Status: No, score=-4.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4]
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 Zmi16FFyIC9I for <vwrap@core3.amsl.com>; Fri, 28 May 2010 09:38:41 -0700 (PDT)
Received: from mga14.intel.com (mga14.intel.com [143.182.124.37]) by core3.amsl.com (Postfix) with ESMTP id C3E513A6A62 for <vwrap@ietf.org>; Fri, 28 May 2010 09:38:41 -0700 (PDT)
Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga102.ch.intel.com with ESMTP; 28 May 2010 09:38:31 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.53,319,1272870000"; d="scan'208";a="282537717"
Received: from rrsmsx603.amr.corp.intel.com ([10.31.0.57]) by azsmga001.ch.intel.com with ESMTP; 28 May 2010 09:38:31 -0700
Received: from rrsmsx601.amr.corp.intel.com (10.31.0.151) by rrsmsx603.amr.corp.intel.com (10.31.0.57) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 28 May 2010 10:38:31 -0600
Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx601.amr.corp.intel.com ([10.31.0.151]) with mapi; Fri, 28 May 2010 10:38:31 -0600
From: "Hurliman, John" <john.hurliman@intel.com>
To: "barryleiba@computer.org" <barryleiba@computer.org>
Date: Fri, 28 May 2010 10:38:28 -0600
Thread-Topic: [vwrap] Moving startup documents into the working group
Thread-Index: Acr+hDSRSTvqQTdGRP6wwj0yUYS3Fw==
Message-ID: <296BA593-D1AA-4831-AD70-197435BBD5C8@intel.com>
References: <AANLkTin1VUFz26_196KCclBEEL3TJMpjb8H_hLY0T9Pv@mail.gmail.com>
In-Reply-To: <AANLkTin1VUFz26_196KCclBEEL3TJMpjb8H_hLY0T9Pv@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "vwrap@ietf.org" <vwrap@ietf.org>
Subject: Re: [vwrap] Moving startup documents into the working group
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2010 16:38:42 -0000

SW50cm9kdWN0aW9uIGFuZCBHb2FscyAtIHllcw0KDQpUcnVzdCBNb2RlbCBhbmQgVXNlciBBdXRo
ZW50aWNhdGlvbiAtIHllcw0KDQpBYnN0cmFjdCBUeXBlIFN5c3RlbSAtIHllcw0KDQpDbGllbnQg
QXBwbGljYXRpb24gTGF1bmNoIE1lc3NhZ2UgLSB5ZXMNCg0KRm91bmRhdGlvbiAtIG5vDQoNCkpv
aG4NCg0KT24gTWF5IDI2LCAyMDEwLCBhdCA2OjE0IFBNLCAiQmFycnkgTGVpYmEiIDxiYXJyeWxl
aWJhLm1haWxpbmcubGlzdHNAZ21haWwuY29tPG1haWx0bzpiYXJyeWxlaWJhLm1haWxpbmcubGlz
dHNAZ21haWwuY29tPj4gd3JvdGU6DQoNCkludHJvZHVjdGlvbiBhbmQgR29hbHMgLSB5ZXMNClRy
dXN0IE1vZGVsIGFuZCBVc2VyIEF1dGhlbnRpY2F0aW9uIC0geWVzDQpBYnN0cmFjdCBUeXBlIFN5
c3RlbSAtIHllcw0KQ2xpZW50IEFwcGxpY2F0aW9uIExhdW5jaCBNZXNzYWdlIC0geWVzDQpGb3Vu
ZGF0aW9uIC0geWVzDQo=

From ohmeadhbh@gmail.com  Fri May 28 10:32:31 2010
Return-Path: <ohmeadhbh@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A3853A67F2 for <vwrap@core3.amsl.com>; Fri, 28 May 2010 10:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 brWJCG7Xb0Yu for <vwrap@core3.amsl.com>; Fri, 28 May 2010 10:32:26 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 6EBBB3A6862 for <vwrap@ietf.org>; Fri, 28 May 2010 10:32:26 -0700 (PDT)
Received: by gyh4 with SMTP id 4so1184564gyh.31 for <vwrap@ietf.org>; Fri, 28 May 2010 10:32:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=fdk6ixA92y2E6JsYBI6QFqNDam//NLTNYJPS5TpoQgE=; b=VASeJR0JmWQ2unMiir2J97i/wPj1v0cFjkWpDuv26aySUL4QF9i8IbBaGS/g67weP5 4mqW+YMhFipztAKOPCN7TohB4SyG1PIN+Xy+DnoHsXd3wWxjzEguddsyvea2WI68LNIM HKqWI8lq/onsfP3HeqoyvxDwd6H53IDZRrVa8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; b=f7/OyJHy7zEl0q/OUpDg7RnhwZl5SYj4Hj0ZRFoTvC4eFHUYcbzXOdcJkdMbVPjnnX Uu2Ii/bYfO/4j2vWGnN+QU8yGeWF+JQ8qu3gNLOL/iTa5qHHk8ulSlkAm23jtbwx+IyH JzDaZrs60cUhJetN0x1mRdJA4Ji5GY0Cnda34=
Received: by 10.224.115.34 with SMTP id g34mr414262qaq.135.1275067933462; Fri,  28 May 2010 10:32:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.189.208 with HTTP; Fri, 28 May 2010 10:31:53 -0700 (PDT)
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Fri, 28 May 2010 10:31:53 -0700
Message-ID: <AANLkTinMc89HxrlNOwLW0m1PQ3cOfaaErfbUUljGbnqA@mail.gmail.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: vwrap@ietf.org
Subject: [vwrap] starting point - client application launch message
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2010 17:32:31 -0000

hmm... strange... the gmail interface puts this message in the same
thread as the others even though it has a different subject line. i'm
changing the subject line even further to try to detach it from the
original thread.

just a quick FYI as to why the CALM message draft exists. The CALM
message draft defines a mime type and format of a message that goes
across the net. The stated use case, to leverage an existing web
authentication structure via OAuth or OpenID, is important to a number
of people in the working group.

I think that's good enough reason to specify it. The last I talked
with John, we were both going to support it. When I left Linden there
were plans to support it in Snowglobe, though obviously I'm not in the
position to task Oz and Merov these days.

It's important to note that it is an informational draft. It's out
there to describe one way of doing things, and it doesn't obligate
anyone to implement it. But putting this specification in front of the
working group allows those of us that do want to use it the ability to
publish what we're doing and solicit comments about it's contents and
use.

I totally get that you're not hip to the spec, and that's okay. I'm
not trying to force you to love it or implement it. Just trying to
explain why some of us other people out here do actually like the idea
of it.

So... to recap:

* it's a useful use case.
* the draft (and subsequent RFC) is required to register the MIME type.
* it describes a message used by two or more implementations.
* it's an informational draft, and is thus entirely optional.
* we're not trying to say the CALM draft is "done," only that we think
it's a good use case and want to use the current draft as a starting
point

-cheers
-meadhbh
--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com



On Fri, May 28, 2010 at 7:52 AM, Morgaine
<morgaine.dinova@googlemail.com> wrote:
> This is a new discussion thread with a new subject line, as Barry request=
ed.
>
> I gave three documents a Yes and two a No, the meaning of "Yes" being as
> Barry said, that they represent a viable starting point --- many large
> changes (to some) will be needed before the "Yes" drafts are anywhere nea=
r
> to being correct and useful though:
>
>> Introduction and Goals - yes
>> Trust Model and User Authentication - yes
>> Abstract Type System - yes
>
> Now regarding my two "No" responses, meaning "not adequate for group
> consideration":
>
>> Client Application Launch Message - no
>> Foundation - no
>
> "Client Application Launch Message" -- this simply has no business being
> part of the VWRAP protocol suite at all.=A0 Launching applications is
> completely outside of our remit I believe, and undoubtedly there will be =
a
> large number of ways of achieving it, depending on the platform.=A0 The
> closest I think we might get to this area is to define the meaning of a
> "landmark" entity (as an URI in the protocol), but blessing one particula=
r
> use of such an entity is quite unnecessary.
>
> "Foundation" --- I gave this a "No" because it appears to be an
> "archeological OGP" document, unearthed from the original days of OGP.=A0=
 It
> does not reflect the OGPX or VWRAP group discussions at all, and is even
> oblivious of the group charter --- notice its attempt to create a single
> "vast, Internet wide virtual world".
>
> What's more, we already have a foundational document --- it's called
> "Introduction and Goals".=A0 Admittedly it's not a very friendly document
> either as background reading nor for the implementer, but nevertheless it=
s
> purpose was to provide the foundation, I believe.=A0 Perhaps the new
> "Foundation" document was a gentle attempt at saying "Unreadable" to the
> first document, and asking for a refactoring?=A0 If so then I'd support t=
hat,
> because currently "Introduction and Goals" is a meandering document with
> little clarity of purpose.=A0 Perhaps "Introduction and Goals" should be
> renamed "Protocol Elements" and have all its background sections removed,
> which would then leave room for an "Introduction" document that would
> provide background and glue for everything else, but no details.
>
> I get the feeling that a big refactoring is due.=A0 Documents have been
> appearing out of the blue without any prior discussion of their need or o=
f
> their scope, as a result of which we currently have a random checkerboard=
 of
> documents, and nothing outside of the type system is particularly well
> described or useful so far.
>
>
> Morgaine.
>
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> On Thu, May 27, 2010 at 2:14 AM, Barry Leiba
> <barryleiba.mailing.lists@gmail.com> wrote:
>>
>> It's time to think about which pre-WG documents the working group is
>> ready to adopt. =A0As I introduce this, I want to stress that adoption
>> of documents does NOT mean that the group has consensus on the current
>> content of those documents, that it collectively agrees with what they
>> say, that the documents are in any sense "ready". =A0All it means is
>> that the working group thinks they're headed in the right direction,
>> and can be used as a starting point for further refinement. =A0Indeed,
>> documents adopted as starting points by the working group might have a
>> number of significant revisions before they are declared "ready" and
>> are sent to the IESG.
>>
>> That said, the chairs would like to take a poll on whether the
>> following are ready for adoption on their next revisions:
>>
>> * Introduction and Goals
>> http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01
>>
>> * Trust Model and User Authentication
>> http://tools.ietf.org/html/draft-hamrick-vwrap-authentication-01
>>
>> * Abstract Type System for the Transmission of Dynamic Structured Data
>> http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00
>>
>> * Client Application Launch Message
>> http://tools.ietf.org/html/draft-hamrick-vwrap-launch-00
>>
>> * Foundation
>> http://tools.ietf.org/html/draft-lentczner-vwrap-foundation-00
>>
>>
>> Please reply in this thread as in this example, listing each document
>> and giving your opinion:
>> > Introduction and Goals - yes
>> > Trust Model and User Authentication - yes
>> > Abstract Type System - yes
>> > Client Application Launch Message - yes
>> > Foundation - yes
>>
>> Please make your opinion either "yes" (the working group should adopt
>> the document) or "no" (the working group should not adopt the
>> document).
>>
>> Please do not discuss anything else in this thread. =A0If you need to
>> discuss your answer, please start a new thread, with a new subject
>> line, for the discussion. =A0If you have any issues you prefer to bring
>> to the chairs off-list, contact us at <vwrap-chairs@tools.ietf.org>.
>>
>> Thanks very much.
>>
>> -- Barry, as chair
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
>

From ohmeadhbh@gmail.com  Fri May 28 11:16:17 2010
Return-Path: <ohmeadhbh@gmail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CEEF3A68C3 for <vwrap@core3.amsl.com>; Fri, 28 May 2010 11:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
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 piFGEr+j2vDB for <vwrap@core3.amsl.com>; Fri, 28 May 2010 11:16:15 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 15CE53A696F for <vwrap@ietf.org>; Fri, 28 May 2010 11:16:14 -0700 (PDT)
Received: by vws11 with SMTP id 11so386149vws.31 for <vwrap@ietf.org>; Fri, 28 May 2010 11:16:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=FpvaP37H72TR2H/faTMKiwiM7sCHY2OP0IYOAjwqR/A=; b=wKdo1dQ/YJSXJldYSjlPBEdUhOWyaoUkRaUjnZ0GsaP6SSE1uI5UmghYIWkLSQaqDs h3/DBGyQJX/4c6mUjz2r26qvfYTJ8oKf9KoqkUEw5WHt/tCwmnRqBZClBl36dx5k3Uw4 8ODtxwLlomyJRusYueX71z8Z+BRIq00Oi5LUg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; b=BMivManoFcQKWkn+XPib7PGi5k1H6g4cj+tBo1GIaSEGquRD+yq79YZ8iv/3tA0z9q 1BN5Hgldb8+pwz63q+8A4edvcemIogHC7b/RCAcusPBtIE+2XIBbQY84pWAuf/mS/DRc YBWICgbSIZ4hrgog/i8yvkldcLp0TaCztfXkA=
Received: by 10.224.35.27 with SMTP id n27mr441205qad.396.1275070561125; Fri,  28 May 2010 11:16:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.189.208 with HTTP; Fri, 28 May 2010 11:15:41 -0700 (PDT)
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Date: Fri, 28 May 2010 11:15:41 -0700
Message-ID: <AANLkTinxwW4khzNJKCS38dGYkvSaG5iu4zxeTUTLAkg1@mail.gmail.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: vwrap@ietf.org
Subject: [vwrap] starting point - foundations
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2010 18:16:17 -0000

For what it's worth...

The intro document is a non-normative, informational introduction to
the problem domain. The foundations document is a normative document
detailing the format and processing expectations of facilities
expected to be... well.. foundational. things that didn't have a place
in other documents but were assumed by the other docs to exist.

i'm not sure why you (morgaine) say that the doc is oblivious to the
charter. both documents are referenced in the charter. i don't
understand what you're getting at.

so... that's why the intro doesn't have a lot of technical content...
it's an informational non normative introduction to the problem
domain. it also elaborates on motivations for decisions made in the
charter (which is why there's a lot of background and informational
text.)

it's also why the foundation doc doesn't have a lot of exposition...
extended exposition and motivation that might have been in it got
moved to the intro.

-cheers
-meadhbh
--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com



On Fri, May 28, 2010 at 7:52 AM, Morgaine
<morgaine.dinova@googlemail.com> wrote:
>
> "Foundation" --- I gave this a "No" because it appears to be an
> "archeological OGP" document, unearthed from the original days of OGP.=A0=
 It
> does not reflect the OGPX or VWRAP group discussions at all, and is even
> oblivious of the group charter --- notice its attempt to create a single
> "vast, Internet wide virtual world".
>
> What's more, we already have a foundational document --- it's called
> "Introduction and Goals".=A0 Admittedly it's not a very friendly document
> either as background reading nor for the implementer, but nevertheless it=
s
> purpose was to provide the foundation, I believe.=A0 Perhaps the new
> "Foundation" document was a gentle attempt at saying "Unreadable" to the
> first document, and asking for a refactoring?=A0 If so then I'd support t=
hat,
> because currently "Introduction and Goals" is a meandering document with
> little clarity of purpose.=A0 Perhaps "Introduction and Goals" should be
> renamed "Protocol Elements" and have all its background sections removed,
> which would then leave room for an "Introduction" document that would
> provide background and glue for everything else, but no details.
>
> I get the feeling that a big refactoring is due.=A0 Documents have been
> appearing out of the blue without any prior discussion of their need or o=
f
> their scope, as a result of which we currently have a random checkerboard=
 of
> documents, and nothing outside of the type system is particularly well
> described or useful so far.
>
>
> Morgaine.
>
>
>
>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> On Thu, May 27, 2010 at 2:14 AM, Barry Leiba
> <barryleiba.mailing.lists@gmail.com> wrote:
>>
>> It's time to think about which pre-WG documents the working group is
>> ready to adopt. =A0As I introduce this, I want to stress that adoption
>> of documents does NOT mean that the group has consensus on the current
>> content of those documents, that it collectively agrees with what they
>> say, that the documents are in any sense "ready". =A0All it means is
>> that the working group thinks they're headed in the right direction,
>> and can be used as a starting point for further refinement. =A0Indeed,
>> documents adopted as starting points by the working group might have a
>> number of significant revisions before they are declared "ready" and
>> are sent to the IESG.
>>
>> That said, the chairs would like to take a poll on whether the
>> following are ready for adoption on their next revisions:
>>
>> * Introduction and Goals
>> http://tools.ietf.org/html/draft-hamrick-vwrap-intro-01
>>
>> * Trust Model and User Authentication
>> http://tools.ietf.org/html/draft-hamrick-vwrap-authentication-01
>>
>> * Abstract Type System for the Transmission of Dynamic Structured Data
>> http://tools.ietf.org/html/draft-hamrick-vwrap-type-system-00
>>
>> * Client Application Launch Message
>> http://tools.ietf.org/html/draft-hamrick-vwrap-launch-00
>>
>> * Foundation
>> http://tools.ietf.org/html/draft-lentczner-vwrap-foundation-00
>>
>>
>> Please reply in this thread as in this example, listing each document
>> and giving your opinion:
>> > Introduction and Goals - yes
>> > Trust Model and User Authentication - yes
>> > Abstract Type System - yes
>> > Client Application Launch Message - yes
>> > Foundation - yes
>>
>> Please make your opinion either "yes" (the working group should adopt
>> the document) or "no" (the working group should not adopt the
>> document).
>>
>> Please do not discuss anything else in this thread. =A0If you need to
>> discuss your answer, please start a new thread, with a new subject
>> line, for the discussion. =A0If you have any issues you prefer to bring
>> to the chairs off-list, contact us at <vwrap-chairs@tools.ietf.org>.
>>
>> Thanks very much.
>>
>> -- Barry, as chair
>> _______________________________________________
>> vwrap mailing list
>> vwrap@ietf.org
>> https://www.ietf.org/mailman/listinfo/vwrap
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>
>
