[p2p-sip] __A_New_Internet-draft_is_available

[slavitch at gmail.com (Michael Slavitch)]

Oh, and one more point.  "

Vigilant and smart to me means the following:

1. Create a WG charter that is in scope with achievable goals.
2. Get the WG approved.
3. Deliver a standard that can be broadly supported.
4. Iterate.

The first part of P2PSIP that should be reliable, self-organizing and
iterative is >us<.



On 8/24/06, Michael Slavitch <slavitch at gmail.com> wrote:
>
>  WHEN YOU CAN MANIPULATE NODES OF MULTIPLE OVERLAYS, WHY NOT MANIPULATE
> THEM TO USE ONLY ONE OVERLAY?
>
>
>  Different overlays will correspond to different groups and regimes, with
> different rules and behaviors. The base overlay connects them together using
> rules of its own.  Overlays that recurse with independent behavior allow for
> rich collaboration based on organized groups with implicit security and
> choice.  Hierarchical, selective or authoritative organization is but a
> subset of self-organization, it is just far more automated.
>
> It is this aspect of overlays, the ability to nest overlays upon each
> other, that makes P2PSIP truly powerful, more powerful than most most could
> even imagine, as the application space changes completely.  Self-organizing
> automated systems could replace much of the cruft and kludge of the
> Internet.  I assert that P2PSIP becomes truly useful if such overlays are
> not only permitted but clearly defined for easy implementation.  It looks
> like P2PSIP will go that way as long as we remain vigilant, supportive and
> smart.
>
> Regards,
>
>
>
>
> On 8/24/06, K.Yamamoto <kyara543 at yahoo.com> wrote:
> >
> > I AGREE HIERARCHICAL MORE EASY AND DISLIKES MESS TOO.
> >
> > BUT UNLESS YOU DELIBERATELY MANIPULATE EVERY MULTI-OVERLAY NODES SO THAT
> > A NODE CAN SAY "HEY, MY CHORD STACK DOES NOT CONNECT WITH ANOTHER CHORD NODE
> > ALSO IN PASTRY OVERLAY BUT CONNECT WITH THE OTHER CHORD NODE ALSO IN BT
> > OVERLAY", OTHERWISE AUTONOMOUS INTERCONNECTION OF MULTI-OVERLAY NODES VERY
> > POSSIBLY WILL FORM A CYCLIC MESH.
> >
> > EXAMPLE: LETS DENOTE A NODE OF MULTI-OVERLAYS X AND Y AS XY.
> > INTERCONNECT NODES ABC, AC AND BC FORMS A MESH.
> >
> > WHEN YOU CAN MANIPULATE NODES OF MULTIPLE OVERLAYS, WHY NOT MANIPULATE
> > THEM TO USE ONLY ONE OVERLAY?
> >
> >
> > THANK YOU.
> >
> > --KY
> > PLEASE QUALITY CONTROL LIKE BUILDING A LEXUS.
> >
> > *Juwei Shi <jwshi at bupt.edu.cn>* wrote:
> >
> >
> > Yes, I agree with Seaward, hierarchically inter-connecting heterogeneous
> > overlays is more practical than the mesh based approach.
> >
> >
> >
> >
> > Interworking among heterogeneous hierarchical is more efficient than do
> > it meshy, you can not expect a flat huge mesh over whole world can work
> > reliably, the reason why mesh is used is the absence of a acceptable
> > standard.
> >
> > Thanks.
> >
> > Seaward
> >
> >
> >  ------------------------------
> > *From:* p2p-sip-bounces at cs.columbia.edu [mailto:p2p-sip-bounces at cs.columbia.edu]
> > *On Behalf Of *K.Yamamoto
> > *Sent:* Thursday, August 24, 2006 2:16 AM
> > *To:* Juwei Shi; p2p-sip at cs.columbia.edu
> > *Subject:* Re: ?????: [p2p-sip] A New Internet-draft is available
> >
> >
> > WHEN NUMEROUS MULTI-OVERLAID NODES ARE INTERCONNECTED, " the
> > interworking among heterogenous overlays" IS GENERALLY MESSY NOT
> > HIERACHICAL.
> >
> > THANK YOU.
> >
> > --KY
> > PLEASE QUALITY
> >  CONTROL LIKE BUILDING A LEXUS.
> >
> > *Juwei Shi <jwshi at bupt.edu.cn>* wrote:
> >
> >    The NAT issues will be discussed in our future drafts.
> > This draft focuses on the interworking among heterogenous overlays and
> > the SIP-over-P2P architecture in one single overlay is proposed by E.
> > Shim etc.
> > http://www.p2psip.org/drafts/draft-shim-sipping-p2p-arch-00.txt
> >  Thanks
> > Juwei
> >  ------------------------------
> >  *??'????oo:* K.Yamamoto [mailto:kyara543 at yahoo.com]
> > *??'?????????:* 2006?1?8 ???23??? 12:21
> > *?"?????oo: *Juwei Shi; p2p-sip at cs.columbia.edu
> > *??????:* Re: [p2p-sip] A New Internet-draft is available
> >  THE DOCUMENT IS GORGEOUS BUT NEED RENAME AS "A MESHY ARCHITECTURE AMONG
> > MULTIPLE P2P-SIP NETWORKS".
> >
> > FOMULA "Node-ID=Hash(Node-IP)" HAS PROBLEM WITH MULTIPLE NODES BEHIND A NAT.
> >
> >  THERE IS LITTLE ABOUT P2P OR SIP, FOR ONE SINGLE OVERLAY.
> >
> >  THANK YOU.
> >
> >  --KY
> >  PLEASE QUALITY CONTROL LIKE BUILDING A LEXUS.
> >
> >
> >
> >
> > *Juwei Shi < jwshi at bupt.edu.cn>* wrote:
> >  Hello, all
> >
> >
> > We have
> >  submitted a new Internet-draft entitled a??A Hierarchical P2P-SIP Architecturea??. This draft focuses
> >  on the SIP-over-P2P architecture and interworking of heterogeneous overlay networks.
> >
> >
> >
> >
> > This document is available in the Internet-drafts archive now:
> > http://www3.ietf.org/internet-drafts/draft-shi-p2psip-hier-arch-00..txt<http://www3.ietf.org/internet-drafts/draft-shi-p2psip-hier-arch-00.txt>
> >  Comments are welcomed!
> >  Thanks
> > Juwei
> >  Juwei Shi
> > Wireless Technology Innovation Institute (WTI)
> > Beijing Univ. of Posts and Telecommunications (BUPT)
> > Tel: [phone] ext. 312
> > Email: jwshi at bupt.edu.cn
> >  _______________________________________________
> > p2p-sip mailing list
> > p2p-sip at cs.columbia.edu
> > https://lists.cs.columbia.edu/cucslists/listinfo/p2p-sip
> >
> >  ------------------------------
> >  Yahoo! Messenger with Voice. Make PC-to-Phone Calls<http://us.rd.yahoo.com/mail_us/taglines/postman1/*http:/usrd.yahoo.com/evt=39663/*http:/voice.yahoo.com>to the US (and 30+ countries) for 2??/min or less.
> >
> >
> >  ------------------------------
> > Yahoo! Messenger with Voice. Make PC-to-Phone Calls
> > <http://us.rd.yahoo.com/mail_us/taglines/postman1/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>to
> > the US (and 30+ countries) for 2?/min or less.
> >
> >
> >  ------------------------------
> > Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small
> > Business
> > <http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/>.
> >
> >
> > _______________________________________________
> > p2p-sip mailing list
> > p2p-sip at cs.columbia.edu
> > https://lists.cs.columbia.edu/cucslists/listinfo/p2p-sip
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.cs.columbia.edu/pipermail/p2p-sip/attachments/20060824/ef18bf97/attachment-0001.html