All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] doc: Add initial 6LoWPAN API definition
Date: Thu, 19 Mar 2015 12:29:36 +0200	[thread overview]
Message-ID: <20150319102936.GB7070@t440s.lan> (raw)
In-Reply-To: <1426760605.3386.38.camel@linux.intel.com>

Hi Jukka,

On Thu, Mar 19, 2015, Jukka Rissanen wrote:
> > +Connect Command
> > +===============
> > +
> > +	Command Code:		0x0004
> > +	Controller Index:	<controller id>
> > +	Command Parameters:	Address (6 Octets)
> > +				Address_Type (1 Octet)
> > +	Return Parameters:	Address (6 Octets)
> > +				Address_Type (1 Octet)
> > +				Network_Interface (16 Octets)
> > +
> > +	This command is used to connect to a remote 6LoWPAN server.
> 
> We should probably say "... remote 6LoWPAN node" here instead.

Indeed. I'll change it.

> > +Disconnect Command
> > +==================
> > +
> > +	Command Code:		0x0005
> > +	Controller Index:	<controller id>
> > +	Command Parameters:	Address (6 Octets)
> > +				Address_Type (1 Octet)
> > +	Return Parameters:	Address (6 Octets)
> > +				Address_Type (1 Octet)
> > +
> > +	This command is used to disconnect from a remote 6LoWPAN server.
> 
> Ditto

Sure.

> > +Start Server Command
> 
> The specification talks about "Router" so should we use same terminology
> here instead of "Server"?

Actually this would be the Node role. So I'll rename it to 'Start Node
Command'.

> > +Stop Server Command
> 
> Ditto.

Sure.

Johan

      reply	other threads:[~2015-03-19 10:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  9:10 [PATCH] doc: Add initial 6LoWPAN API definition Johan Hedberg
2015-03-19 10:22 ` Szymon Janc
2015-03-19 10:28   ` Johan Hedberg
2015-03-19 10:23 ` Jukka Rissanen
2015-03-19 10:29   ` Johan Hedberg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150319102936.GB7070@t440s.lan \
    --to=johan.hedberg@gmail.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.