Re: [stir] I-D Action: draft-kaplan-stir-ikes-out-00.txt

[<[e-mail]>]

Hadriel,

A couple of initial questions/comments on this draft. 

Just an observation, first. Sometimes in 4.1 and 4.2 (see below), definitions seem to refer to numbers in general, examples taken from the NANP,... and some conclusion drawn essentially from an observation on the example rather than from the definition. :) 

> IKES also considers toll-free 1-8xx type numbers to be "E.164" numbers, 
> even though technically they are not.

If the statement is not only about US toll free numbers but on "freephone" numbers in general ("cc-8xx" being indeed very common for that), "technically they may not be", would be more accurate I think, on other CCs some of them are actually reachable from abroad. 

> Nationally-specific number codes are numbers that are not E.164 
>   numbers, nor are private numbering plan numbers, but are instead 
>   number codes used for specific purposes within national numbering 
>   plans.  Examples of these are N11 codes in the NANP, two or three 
>   digit emergency numbers such as 112, and inter-carrier common short 
>   codes.  Even if they cannot be used as caller-id numbers , they are 
>   destination numbers and thus IKES needs to support them.  

Actually short codes can sometimes be used as CgPN, again it depends on the country. Probably not emergency numbers, (although you might even find corner cases in the European 116 series, some of which qualify as such in some countries) but short codes can be. 

>   Likewise for nationally-specific number codes, the IKES process 
>   generates a canonical representation of the number code.  A leading 
>   country-code is prepended to the number code, to indicate the 
>   national numbering plan they are for.

I suppose you've been waiting for this but the usual problem of using such "pseudo E.164 numbers" for non E.164 numbers instead of local numbers is that, for countries that use national trunk codes eg 0, you can have an overlap between the short codes and the initial digits of the E.164 NDC or the SN. It's obviously not a problem as long as we stay in the dialing plan (actually that's precisely what the national trunk code is here for, to have more spare values to use) but it seems this would mean that the assignee of say range 112 could legitimately sign +CC-112, I'm not sure that's a good thing. (although this particular one 112 is indeed generally reserved in the national E.164 numbering plan but I use it to get the picture). 

> 10.  Usage in SS7/ISUP
[...]
> the signature, key 
>   index, and timestamp are carried in the User-to-User Information 
>   parameter ;

(Noted past exchanges on this. Don't think this was addressed) Generally speaking, what if the UUI is already used for a different purpose? (eg RFC 6467 use cases)

Thanks, 

Philippe Fouquart
Orange Labs Networks
[phone]


-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Hadriel Kaplan
Sent: Friday, July 12, 2013 6:39 AM
To: [e-mail]
Subject: [stir] I-D Action: draft-kaplan-stir-ikes-out-00.txt

Howdy,
I've been meaning to submit a couple drafts for STIR - one for how a DNS model could work, and one for how the stuff can get through SIP and other protocols in-band.

Since some of the recent discussion has touched on some of the issues, and the deadline for new drafts is fast approaching, I've submitted the latter draft just now:
http://tools.ietf.org/html/draft-kaplan-stir-ikes-out-00

Sorry about the length, and yes it's still drafty/straw-man-ish.  It's also repetitive in sections, and needs a re-write, but the general concept should be understandable.

Comments/flames appreciated.

-hadriel


Begin forwarded message:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
> 	Title           : An Identity Key-based and Effective Signature for Origin-Unknown Types
> 	Author(s)       : Hadriel Kaplan
> 	Filename        : draft-kaplan-stir-ikes-out-00.txt
> 	Pages           : 28
> 	Date            : 2013-07-11
> 
> Abstract:
>   This document describes a mechanism and format for signing source
>   identity information of communication requests, in a manner capable
>   of crossing multiple communication protocol types - even if the
>   origin's protocol type is unknown.  This is useful for providing
>   E.164 and other forms of Caller-ID reputability for various
>   communication protocols, such as SIP, XMPP, WebRTC, H.323, and
>   SS7/ISUP.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-kaplan-stir-ikes-out
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-kaplan-stir-ikes-out-00
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

_______________________________________________
stir mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/stir

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.