From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.236.154.227 with SMTP id h63cs405478yhk; Mon, 11 Jul 2011 06:54:16 -0700 (PDT) Return-Path: <9front+bncCLqU4qzTHBCEgezwBBoEiFYoUg@googlegroups.com> Received-SPF: pass (google.com: domain of 9front+bncCLqU4qzTHBCEgezwBBoEiFYoUg@googlegroups.com designates 10.236.78.137 as permitted sender) client-ip=10.236.78.137; Authentication-Results: mr.google.com; spf=pass (google.com: domain of 9front+bncCLqU4qzTHBCEgezwBBoEiFYoUg@googlegroups.com designates 10.236.78.137 as permitted sender) smtp.mail=9front+bncCLqU4qzTHBCEgezwBBoEiFYoUg@googlegroups.com; dkim=pass header.i=9front+bncCLqU4qzTHBCEgezwBBoEiFYoUg@googlegroups.com Received: from mr.google.com ([10.236.78.137]) by 10.236.78.137 with SMTP id g9mr1638302yhe.1.1310392455971 (num_hops = 1); Mon, 11 Jul 2011 06:54:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:date :message-id:subject:from:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type :content-transfer-encoding; bh=jgyduHHZXgJpH+pq1vrB1T68gDqmdLJlN5twpWgcLaU=; b=IU3aYnWUt17KVYvh1X58IQgw0Cb0uEczItxo14wXC6BbAtaWQTQgrNYyA0b+PIlvTe o7iN4a/g5tOBwsCSEk6lxNDlRSr5qsa/KQjyorJsedypRowZHxKRa9ripiti1sTZ7tO/ J2j4yjaM+T7fYSYxd2z1fNNY8HLMK1YFQU7mU= Received: by 10.236.78.137 with SMTP id g9mr490246yhe.1.1310392452034; Mon, 11 Jul 2011 06:54:12 -0700 (PDT) X-BeenThere: 9front@googlegroups.com Received: by 10.231.83.11 with SMTP id d11ls3190993ibl.1.gmail; Mon, 11 Jul 2011 06:54:11 -0700 (PDT) Received: by 10.42.151.7 with SMTP id c7mr1171806icw.44.1310392451573; Mon, 11 Jul 2011 06:54:11 -0700 (PDT) Received: by 10.42.151.7 with SMTP id c7mr1171805icw.44.1310392451564; Mon, 11 Jul 2011 06:54:11 -0700 (PDT) Received: from mail-iy0-f171.google.com (mail-iy0-f171.google.com [209.85.210.171]) by gmr-mx.google.com with ESMTPS id n12si5195093icr.0.2011.07.11.06.54.11 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Jul 2011 06:54:11 -0700 (PDT) Received-SPF: pass (google.com: domain of andreasbwagner@gmail.com designates 209.85.210.171 as permitted sender) client-ip=209.85.210.171; Received: by iyi12 with SMTP id 12so5579144iyi.16 for <9front@googlegroups.com>; Mon, 11 Jul 2011 06:54:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.42.12 with SMTP id q12mr4588685ibe.81.1310392451376; Mon, 11 Jul 2011 06:54:11 -0700 (PDT) Received: by 10.231.10.66 with HTTP; Mon, 11 Jul 2011 06:54:11 -0700 (PDT) In-Reply-To: <20110711090309.4d675556@lahti.ethans.dre.am> References: <20110711090309.4d675556@lahti.ethans.dre.am> Date: Mon, 11 Jul 2011 15:54:11 +0200 Message-ID: Subject: Re: streaming 9p From: Andreas Wagner To: 9front@googlegroups.com X-Original-Sender: andreasbwagner@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of andreasbwagner@gmail.com designates 209.85.210.171 as permitted sender) smtp.mail=andreasbwagner@gmail.com; dkim=pass (test mode) header.i=@gmail.com Reply-To: 9front@googlegroups.com Precedence: list Mailing-list: list 9front@googlegroups.com; contact 9front+owners@googlegroups.com List-ID: <9front.googlegroups.com> X-Google-Group-Id: 831096995978 List-Post: , List-Help: , List-Archive: Sender: 9front@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > Any chance you could summarize how CCN works? I started to read Jacobson.= pdf but haven't got the time to read enough to discover whether it will mak= e my eyes bleed. My first impression is it's like using torrents for everyt= hing but with some different discovery mechanism. > > Perhaps more importantly (and possibly simpler), could you summarize how = unique names are constructed for CCN data, please? > CCN does not have anything to do with bittorrent. With CCN content/names are the primitives rather than locations/ip addresses, in other words location is decoupled from content, identity and access. At first it may seem that CCN is only useful for static content, however VoCCN (Voice over CCN) exists and eliminates the need for the middleware. Mobility is a non-issue with CCN because content does not need to be mapped to a location. From what I can see the CCNx implementation works on top of IP although CCN intended to replace TCP/IP. CCN names can have a unique dns domain name prefix for connectivity better connectivity over the internet. An "Interest packet" is forwarded on a "face" when the prefix of its name matches a prefix of a name in the Forwarding Information Base, when the name of an Interest Packet satisfies (matches) the name of a "Data packet" the data packet is forwarded downstream following the Pending Interest Table (breadcrumb) entries. In many ways CCN is similar to TCP/IP because the designers did not want unnecessarily to throw out what has worked with TCP/IP. I am looking into porting ccn to 9front for use with the filesystem and 9p. I guess I the filesystem would be the ccn data repository and the ccn names would be the filenames and directory paths.