[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [seamoby] BOF: IP over Bluetooth for 50th Meeting of IETF.



Your concerns will be addressed in a favourable manner.
Please join the list.  Your input is very welcome.

- Kulwinder.

> -----Original Message-----
> From: James Kempf [mailto:kempf@xxxxxxxxxxxxxxxxxxxxxx]
> Sent: Monday, February 12, 2001 1:18 PM
> To: zeroconf@xxxxxxxxx; seamoby@xxxxxxxxxxxxx;
> MOBILE-IP@xxxxxxxxxxxxxxxxxxxxxxxxxxxx; srvloc@xxxxxxxxxx;
> aaa-wg@xxxxxxxxx; manet@xxxxxxxxxxxxxxxx; ipsec@xxxxxxxxxxxxxxxxx;
> ipsec-policy@xxxxxxxx; ietf-ipsra@xxxxxxxx; ietf-sacred@xxxxxxx;
> enum@xxxxxxxx; sigtran@xxxxxxxxxxxxxxxxxxxxxxxxxxxx; ietf@xxxxxxxx;
> IETF-Announce@xxxxxxxx; BLUETOOTH-BOF@xxxxxxxxxxxxxxxxxxxxx;
> kulwinder.atwal@xxxxxxxxxxxxxxxx
> Cc: narten@xxxxxxxxxxxxxxx; Ron.Akers@xxxxxxxxxxxx
> Subject: Re: [seamoby] BOF: IP over Bluetooth for 50th 
> Meeting of IETF. 
> 
> 
> Kulwinder,
> 
> There is an issue here with the closed, proprietary nature of 
> the Bluetooth
> SIG. Since information on what the SIG is doing is not available until
> it is complete, there is nothing to prevent the SIG from 
> doing something
> that would invalidate the work that IETF puts into desiging a better
> IP over Bluetooth.
> 
> Is there any possibility of gaining assurance from the SIG that they
> won't do something like this?
> 
> 		jak
> 
> 
> >
> >Myself and Ron Akers have requested an IP over Bluetooth BOF 
> for the 50th
> >Meeting of the IETF in Minneapolis.  The BOF will discuss 
> the creation of a
> >IETF Working Group to investigate the most open and 
> efficient way to place
> >IP over the Bluetooth Host Controller.
> >
> >Current work in this area within the Bluetooth SIG 
> concentrates on defining
> >IP over a set of other lower-layer stacks. Currently there 
> are two options
> >defined by the Bluetoth SIG:
> >
> > Option 1: IP/PPP/RFCOM/L2CAP/Host Controller
> >
> > Option 2: IP/PAN Profile/L2CAP/Host Controller
> > 	   (where the PAN Profile is a Bluetooth SIG work in progress)
> > 
> >
> >We are proposing that the IETF form a WG to define a more 
> efficient way of
> >running IP over Bluetooth. In particular, IP would run
> > over an IETF protocol over the Host Controller without 
> L2CAP.  This option
> >may be adopted by the Bluetooth SIG at a later date as a 
> Profile.  Since all
> >Bluetooth SIG Profiles are optional, a customer may choose 
> any combination
> >of Profiles in a final product.  Further, since Bluetooth 
> Working Groups
> >have it in their mandate to adopt protocols from other 
> standards making
> >bodies such as the IETF, there exists a clear path for IETF 
> work to be
> >adopted by the Bluetooth SIG.
> > 
> >Whereas the last BOF was informational only and organized by 
> the Bluetooth
> >SIG itself, the objective of this BOF will be to foster 
> innovation, and
> >speed progress by placing IP related protocol development 
> wihin the IETF and
> >Bluetooth-specific protocol development
> > within the Bluetooth SIG, by developing an IP over 
> Bluetooth IETF Working
> >Group.
> > 
> >This effort will define its own way of running IP over Bluetooth, by
> >carefully selecting a set of Bluetooth protocols (freely 
> available from
> >published specifications at
> >http://www.bluetooth.com/developer/specification/specificatio
> n.asp) on which
> >to build IP.
> >
> >Please join myself, Kulwinder Atwal, and Ron Akers on the 
> pre-BOF mailing
> >list:
> > 
> >This site runs version 2.0.1 of the "Mailman" list manager.  
> >The following describes commands you can send to get
> >information about, and control your subscription to the lists at
> >this site. Note that much of the following can also be 
> >accomplished via the World Wide Web, at:
> >
> >    http://internet.motlabs.com/mailman/listinfo/bluetooth
> >
> >In particular, you can use the Web site to have your password sent to
> >your delivery address.
> >
> >Email commands can be in the subject line or in the body 
> >of the message. The commands should be set to the following address:
> >
> >  <bluetooth-request@xxxxxxxxxxxxxxxxxxxx>
> >
> >About the descriptions - words in "<>"s signify REQUIRED items and
> >words in "[]" denote OPTIONAL items.  Do not include the "<>"s or
> >"[]"s when you use the commands.
> >
> >The following commands are valid:
> >
> >    subscribe [password] [digest-option] [address=<address>]
> >        Subscribe to the mailing list.  Your password must 
> be given to
> >        unsubscribe or change your options.  When you 
> subscribe to the
> >        list, you'll be reminded of your password periodically.
> >        'digest-option' may be either: 'nodigest' or 'digest' (no
> >        quotes!)  If you wish to subscribe an address other than the
> >        address you send this request from, you may specify
> >        "address=<email address>" (no brackets around the email
> >        address, no quotes!)
> >
> >    unsubscribe <password> [address]
> >        Unsubscribe from the mailing list.  Your password must match
> >        the one you gave when you subscribed.  If you are trying to
> >        unsubscribe from a different address than the one you
> >        subscribed from, you may specify it in the 'address' field.
> >
> >    who
> >        See everyone who is on this mailing list.
> >
> >    info
> >        View the introductory information for this list.
> >
> >    lists
> >        See what mailing lists are run by this Mailman server.
> >
> >    help
> >        This message.
> >
> >    set <option> <on|off> <password> 
> >        Turn on or off list options.  Valid options are:
> >
> >        ack:
> >            Turn this on to receive acknowledgement mail 
> when you send
> >            mail to the list.
> >
> >        digest:
> >            Receive mail from the list bundled together 
> instead of one
> >            post at a time.
> >
> >        plain:
> >            Get plain-text, not MIME-compliant, digests (only if
> >            digest is set)
> >
> >        nomail:
> >            Stop delivering mail.  Useful if you plan on taking a
> >            short vacation.
> >
> >        norcv:
> >            Turn this on to NOT receive posts you send to the list.
> >            Does not work if digest is set.
> >
> >        hide:
> >            Conceals your address when people look at who is on this
> >            list.
> >
> >
> >    options
> >        Show the current values of your list options.
> >
> >    password <oldpassword> <newpassword> 
> >        Change your list password.
> >    
> >    end or --
> >       Stop processing commands (good to do if your mailer
> >       automatically adds a signature file - it'll save you 
> from a lot
> >       of cruft).
> >
> >
> >Commands should be sent to bluetooth-request@xxxxxxxxxxxxxxxxxxxx
> >
> >Questions and concerns for the attention of a person should 
> be sent to
> >
> >    bluetooth-admin@xxxxxxxxxxxxxxxxxxxx
> >
> >
> >
> >Kulwinder Atwal
> >Bluetooth Design
> >Zucotto Wireless Inc.
> >kulwinder.atwal@xxxxxxxxxxx
> >
> >------------------------------------------------------------
> >Ron Akers                               Voice :(847)576-7928
> >Networks and Infrastructure Research      FAX :(847)576-3240
> >Motorola Laboratories           email:ron.akers@xxxxxxxxxxxx 
> >1301 Algonquin Rd, Rm 2246
> >Schaumburg, IL. 60196
> >------------------------------------------------------------
>