Re: [Softwires] Updates on H&S framework draft
"Greg Shepherd" <gjshep@gmail.com> Mon, 19 March 2007 17:57 UTC
Return-path: <softwires-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTM6U-0002wV-Aa; Mon, 19 Mar 2007 13:57:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTM6S-0002vp-EB for softwires@ietf.org; Mon, 19 Mar 2007 13:57:04 -0400
Received: from nf-out-0910.google.com ([64.233.182.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTM6Q-0001h2-Sa for softwires@ietf.org; Mon, 19 Mar 2007 13:57:04 -0400
Received: by nf-out-0910.google.com with SMTP id l36so1200909nfa for <softwires@ietf.org>; Mon, 19 Mar 2007 10:57:02 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=HV0hlNqEvF4l9TDsFhg5eVfXAy5dgAA6tJLqPbZyAA0yBSpvUoRPV8tKaEjWNa3EOHYPMkG6HZLZmTHWx/zJH2ULOVB31y0/iwuAwBNEeVa1eLC5F0UCmLKACPt63mtuFyieNkB3I8S3JEncHAuXj0vaHWPlKI4MPh2jSGlwgA8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=COEzab3Se3XKUIjGPJtHAIt69i5Kt8WgBLtsMnLhkNDN8FBA0MXH4UMLEgUPLchiWYNuwmRzxxh/rU96mwLVawQ3gDEZwxG2qrnMKx3xhuRsVK1amGN9Au8ORj3WWy4BynycXEqURiwotrK0axXFIzs93bg1PbxLIazcrmCVAR8=
Received: by 10.78.20.13 with SMTP id 13mr2548699hut.1174327021074; Mon, 19 Mar 2007 10:57:01 -0700 (PDT)
Received: by 10.78.14.18 with HTTP; Mon, 19 Mar 2007 10:57:00 -0700 (PDT)
Message-ID: <38c19b540703191057x23368afag1715c2de6d45f72b@mail.gmail.com>
Date: Mon, 19 Mar 2007 10:57:00 -0700
From: Greg Shepherd <gjshep@gmail.com>
To: Bruno STEVANT <bruno.stevant@enst-bretagne.fr>
Subject: Re: [Softwires] Updates on H&S framework draft
In-Reply-To: <97909878-8CE2-4042-B04E-683B382EA4E7@enst-bretagne.fr>
MIME-Version: 1.0
References: <E11E234A-3DA0-46B2-A472-0D3AE4110C3C@enst-bretagne.fr> <38c19b540703191007j55028465yb2dca3ca38ba7d99@mail.gmail.com> <97909878-8CE2-4042-B04E-683B382EA4E7@enst-bretagne.fr>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: softwires@ietf.org
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0759177875=="
Errors-To: softwires-bounces@ietf.org
On 3/19/07, Bruno STEVANT <bruno.stevant@enst-bretagne.fr> wrote: > > For the Mesh framework, it makes sense to have multicast > considerations included in the Framework document. > For the H&S framework, deploying multicast is mostly to give to the > involved components of a Softwire a role in the multicast topology. > No special encap., signaling, etc. I was addressing the question as to whether the hub is part of the L3 infrastructure (and therefore running PIM) or is just an L2 dumb hub (transiting/broadcasting PIM messages to the other spokes) - neither appear as deployment-only issues to me. Either way it will need some mcast smarts and should be addressed in the draft. But there is still some scenarios to explore : ASM/SSM, emmitter and > receiver between SI ... This will probably be part of a separate > document, which will be guidelines for deployment. Again, I don't see these as deployment issues but as actual hub functionality issues. Greg Le 19 mars 07 à 18:07, Greg Shepherd a écrit : > > > While I agree with the mcast portion of the draft - mcast protocols > > run over the tunnels - there's no mention of the protocol end- > > points; ie - is the hub expected to be part of the mcast topology, > > replicating accordingly? > > > > Thanks, > > Greg > > > > On 2/16/07, Bruno STEVANT <bruno.stevant@enst-bretagne.fr> wrote: > > Hi all, > > > > Carlos and I finally got an update on the H&S draft out yesterday. > > http://www.ietf.org/internet-drafts/draft-ietf-softwire-hs-framework- > > l2tpv2-03.txt > > > > Now we ask to anyone on the list to take 10 minutes of their time and > > read this version carefully. > > Any remarks and comments are welcome ! From these feedbacks we hope > > to release a new version before the cut-off for Prague. > > > > Enjoy your read ! > > -- > > Bruno STEVANT - ENST Bretagne > > > > > > > > _______________________________________________ > > Softwires mailing list > > Softwires@ietf.org > > https://www1.ietf.org/mailman/listinfo/softwires > > > > -- > Bruno STEVANT - ENST Bretagne > > >
_______________________________________________ Softwires mailing list Softwires@ietf.org https://www1.ietf.org/mailman/listinfo/softwires
- [Softwires] Updates on H&S framework draft Bruno STEVANT
- Re: [Softwires] Updates on H&S framework draft Greg Shepherd
- Re: [Softwires] Updates on H&S framework draft Bruno STEVANT
- Re: [Softwires] Updates on H&S framework draft Greg Shepherd
- Re: [Softwires] Updates on H&S framework draft Bruno STEVANT
- Re: [Softwires] Updates on H&S framework draft Greg Shepherd