[email protected] 48 aug. 2000 # 1 orit levin, director of product management...

10
[email protected] IETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management Orit Levin, Director of Product Management [email protected]

Upload: owen-watson

Post on 27-Mar-2015

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Orit@radvision.comIETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management orit@radvision.com

[email protected] IETF 48 Aug. 2000 # 1

Orit Levin, Director of Product ManagementOrit Levin, Director of Product Management

[email protected]

Page 2: Orit@radvision.comIETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management orit@radvision.com

H323-URLH323-URL

““draft-levin-h323-url-scheme-00.txt”

[email protected]

IETF 48 August 2000IETF 48 August 2000

Page 3: Orit@radvision.comIETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management orit@radvision.com

[email protected] IETF 48 Aug. 2000 # 3

The GoalsThe Goals

Publish H323-URL definition as an Informational RFC

Register H323-URL with IANA

Page 4: Orit@radvision.comIETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management orit@radvision.com

[email protected] IETF 48 Aug. 2000 # 4

H323-URL USEH323-URL USE

A pointer to H.323 “service”

To be carried in H.323 messages

To be used in web pages

etc.

Page 5: Orit@radvision.comIETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management orit@radvision.com

[email protected] IETF 48 Aug. 2000 # 5

H.225.0 “Alias” DefinitionH.225.0 “Alias” Definition

AliasAddress ::= CHOICE{

e164 IA5String (SIZE (1..128)) (FROM ("0123456789#*,")),h323-ID BMPString (SIZE (1..256)), -- Unicode...,url-ID IA5String (SIZE(1..512)), -- URL style addresstransportID TransportAddress,email-ID IA5String (SIZE(1..512)), -- rfc822partyNumber PartyNumber

}

Page 6: Orit@radvision.comIETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management orit@radvision.com

[email protected] IETF 48 Aug. 2000 # 6

H323-URL SyntaxH323-URL Syntax

H323-URL = "H323:" ( user / "@" hostport/ user "@" hostport )

user = unreserved / escapedhostport = host [ ":" port]host = hostname / IPv4address / IPv6referencehostname = *( domainlabel "." ) toplabel [ "." ]domainlabel = alphanum / alphanum *( alphanum / "-" ) alphanumtoplabel = ALPHA / ALPHA *( alphanum / "-" ) alphanumIPv4address = 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGITIPv6reference = "[" IPv6address "]"IPV6address = hexpart [ ":" IPv4address ]hexpart = hexseq / hexseq "::" [ hexseq ] / "::" [ hexseq ]hexseq = hex4 *( ":" hex4 )hex4 = 1*4HEXDIGport = 1*DIGITunreserved = alphanum / markalphanum = ALPHA / DIGITmark = "-" / "_" / "." / "!" / "~" / "*" / "'"

/ "(" / ")" / "&" / "=" / "+" / "$" / ","escaped = "%" HEXDIG HEXDIG

Page 7: Orit@radvision.comIETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management orit@radvision.com

[email protected] IETF 48 Aug. 2000 # 7

H323-URL (Continued)H323-URL (Continued)

Commonalties The H.323 URL host portion is Case Insensitive

The host numbers are defined to be used without square brackets

H.323 Specific issues GK Identifier as a part of “host” portion

Page 8: Orit@radvision.comIETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management orit@radvision.com

[email protected] IETF 48 Aug. 2000 # 8

MilestonesMilestones

H323-URL will be included in H.323v.4

H.323v.4 decision is due November 2000

H323-URL will be maintained and developed as a part of H.323 Annex O “Internet Technologies Complementary to H.323”

Additional parameters are for consideration

Page 9: Orit@radvision.comIETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management orit@radvision.com

[email protected] IETF 48 Aug. 2000 # 9

Registration of the URL schemeRegistration of the URL scheme

According to BCP-35 (RFC2717)

Two alternatives for registration of the

“scheme name”

IETF Tree

An alternate (ITU ?) Tree

Page 10: Orit@radvision.comIETF 48 Aug. 2000 # 1 Orit Levin, Director of Product Management orit@radvision.com

[email protected] IETF 48 Aug. 2000 # 10 [email protected]