Re: Comments on Trunk Group ID and RE: [Iptel] gettinggroupconsensuson moving forward with our workitems

[Takuya Sawada <[e-mail]>]

Hi,

As per ABNF in 2806bis, local-number format MUST have phone-context
parameter. So, for example,

tel:-;phone-context=gateway.example.com;tgrp=foo

conforms to the rule in 2806bis.
You can reserve any number format for void-number, "-" or "####"
or whatever, under an administrative domain, e.g. "gateway.example.com".

I think this is an acceptable solution because tgrp draft says in 4.2;
"The use of the "phone-context" parameter in conjunction with this
draft is mandatory".
If we still want global void-number format for tel URI to indicate
tel-related properties without number, we need some more
work in 2806bis.
(This can be used with cpc parameter, if adopted.)

Regards,
Takuya Sawada


> Gone thru 2806bis-09 one more time, global-number-digits and
> local-number-digits are defined as:
> 
> global-number-digits = "+" 1*phonedigit
> local-number-digits  = 1*phonedigit-hex
> <snip>
> phonedigit           = DIGIT / [ visual-separator ]
> phonedigit-hex       = HEXDIG / "*" / "#" / [ visual-separator ]
> visual-separator     = "-" / "." / "(" / ")"
> 
> So would this be valid: "tel:-;tgrp=foo"?
> 
> Thanks, Shan Lu
> 
> >-----Original Message-----
> >From: [e-mail] [mailto:[e-mail]] 
> >On Behalf Of Shan Lu
> >Sent: Monday, November 15, 2004 10:09 AM
> >To: 'list iptel'
> >Subject: RE: Comments on Trunk Group ID and RE: [Iptel] 
> >getting groupconsensuson moving forward with our workitems
> >
> >
> >Dave,
> >
> >Based on 2806bis-09, tel:;tgrp=foo is not valid. I am on the 
> >fence whether
> >it ought to be.
> >
> >Thanks, Shan Lu
> >
> >>From draft-ietf-iptel-rfc2806bis-09:
> >
> >   telephone-uri        = "tel:" telephone-subscriber
> >   telephone-subscriber = global-number / local-number
> >   global-number        = global-number-digits *par
> >   local-number         = local-number-digits *par context *par
> >   <snip>
> >   global-number-digits = "+" 1*phonedigit
> >   local-number-digits  = 1*phonedigit-hex
> >
> >>-----Original Message-----
> >>From: [e-mail] [mailto:[e-mail]] 
> >>On Behalf Of David R Oran
> >>Sent: Monday, November 15, 2004 8:05 AM
> >>To: Shan Lu
> >>Cc: 'list iptel'
> >>Subject: Re: Comments on Trunk Group ID and RE: [Iptel] 
> >>getting groupconsensus on moving forward with our workitems
> >>
> >>
> >>Is tel:;tgrp=foo not a valid tel: url?
> >>If not, it ought to be.
> >>
> >>On Nov 12, 2004, at 3:49 PM, Shan Lu wrote:
> >>
> >>> I support the plan to move forward with the trunk group draft. In  
> >>> fact, my
> >>> company intends to implement it.
> >>>
> >>> However, I do believe there exists a technical hole in the draft,  
> >>> which I
> >>> raised on the list before. That is, since "tgrp" is defined as a  
> >>> tel-uri
> >>> parameter, it can not exist on its own without the actual tel-uri  
> >>> number. In
> >>> the case of originating trunk group (ie. PSTN-to-IP 
> >direction), the  
> >>> calling
> >>> number may be absent. The question is then how to express 
> >>originating  
> >>> trunk
> >>> group.
> >>>
> >>> Thanks,
> >>>
> >>> Shan Lu
> >>>
> >>>> -----Original Message-----
> >>>> From: [e-mail] [mailto:[e-mail]]
> >>>> On Behalf Of Jonathan Rosenberg
> >>>> Sent: Tuesday, November 09, 2004 4:03 PM
> >>>> To: list iptel
> >>>> Subject: [Iptel] getting group consensus on moving forward
> >>>> with our workitems
> >>>>
> >>>>
> >>>> Folks,
> >>>>
> >>>> At the iptel meeting today, there was consensus in the room on
> >>>> plans for
> >>>> moving forward with various drafts. I'd like to verify that
> >>>> consensus by
> >>>> asking the list if folks are OK proceeding with the following:
> >>>>
> >>>> * Proceed to wglc on draft-ietf-iptel-tel-np once a revision
> >>>> appears in
> >>>> the archives
> >>>>
> >>>> * Proceed to wglc on
> >>>> http://www.ietf.org/internet-drafts/draft-ietf-iptel-trunk-grou
> >>> p-02.txt
> >>> immediately following the ietf
> >>>
> >>> * adopt
> >>> http://www.ietf.org/internet-drafts/draft-stastny-iptel-tel-enumdi 
> >>> -00.txt
> >>> as a work item of iptel
> >>>
> >>> * do not adopt
> >>> 
> >>http://www.ietf.org/internet-drafts/draft-rosen-iptel-dialstri
> >ng-00.txt
> >>> as a work item. The author will take it directly to IESG as an
> >>> individual draft.
> >>>
> >>> * do not adopt the expired tel cpc draft
> >>> 
> >(http://www.watersprings.org/pub/id/draft-mahy-iptel-cpc-01.txt) as a
> >>> work item. If folks have a problem that they believe is addressed by
> >>> this work, please bring that forward in the next few weeks.
> >>>
> >>> * tgrep will go to IESG after a revision incorporating comments from
> >>> Cullen and the pending comments from Jonathan
> >>>
> >>> Thanks,
> >>> Jonathan R.
> >>> -- 
> >>> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> >>> Director, Service Provider VoIP Architecture   Parsippany, NJ  
> >>> 07054-2711
> >>> Cisco Systems
> >>> [e-mail]                              FAX:   [phone]
> >>> http://www.jdrosen.net                         PHONE: [phone]
> >>> http://www.cisco.com
> >>>
> >>>
> >>> _______________________________________________
> >>> Iptel mailing list
> >>> [e-mail]
> >>> https://www1.ietf.org/mailman/listinfo/iptel
> >>>
> >>>
> >>> _______________________________________________
> >>> Iptel mailing list
> >>> [e-mail]
> >>> https://www1.ietf.org/mailman/listinfo/iptel
> >>>
> >>David R. Oran
> >>Cisco Fellow
> >>Cisco Systems
> >>7 Ladyslipper Lane
> >>Acton, MA 01720 USA
> >>Tel: [phone]
> >>Email: [e-mail]
> >>
> >>
> >>_______________________________________________
> >>Iptel mailing list
> >>[e-mail]
> >>https://www1.ietf.org/mailman/listinfo/iptel
> >>
> >
> >
> >_______________________________________________
> >Iptel mailing list
> >[e-mail]
> >https://www1.ietf.org/mailman/listinfo/iptel
> >
> 
> 
> _______________________________________________
> Iptel mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/iptel


--------
Takuya Sawada
KDDI Corporation (KDDI)
Garden Air Tower, 3-10-10, Iidabashi, 
Chiyoda-ku, Tokyo 102-8460, Japan
Tel: [phone]
Fax: [phone]
[e-mail]

_______________________________________________
Iptel mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/iptel