Re: Comments on RFC2806bis

> 
> Is there a reason why "context" is put inside ()? 

No, but it doesn't matter, since the () are just grouping. I removed the ().

 >
  Also, the syntax allows
> more than one "context" parameter.  Is it possible to have more than one
> "context" in real situation?  If yes (e.g., two domain names plus one
> prefix), which one is to be used?  Suggest to add some discussions about the
> allowed situation where more than one contexts occur.

This was supposed to be an "OR", i.e., the number applies in all such 
contexts. However, come to think of it, that's probably a bad idea. I 
don't think URIs typically have multiple parameters with the same name. 
Some parsers are likely to not take this gracefully. For the OR case, 
the pickings are slim, however:

- + is taken
- comma and semicolon are not allowed (without escaping)
- / doesn't fit well and would be confusing
- . doesn't work for domain names
- : is one possibility, as in

tel:1234;phone-context=example.com:+12345

Other suggestions welcome.

> 
> I've the "global routing number" parameter that begin with the country code
> followed by hex digits.  Is it possible for you to describe "country code"
> part of the global-number-part so that I can use it in my I-D.  I hate to
> see that the "extensions" defines something in more details.  The first one
> to three digits of the global-number-part identify the country code.

Done. Can the country code contain hex digits? Is there the possibility 
that country codes need more than three digits? Does East Timor have its 
own country code?