Skip to main content

H.248/MEGACO Registration Procedures
draft-groves-megaco-pkgereg-04

Yes

(Cullen Jennings)

No Objection

(Adrian Farrel)
(Alexey Melnikov)
(Dan Romascanu)
(Lisa Dusseault)
(Magnus Westerlund)
(Ralph Droms)
(Ron Bonica)
(Ross Callon)

Note: This ballot was opened for revision 04 and is now closed.

Cullen Jennings Former IESG member
Yes
Yes () Unknown

                            
Adrian Farrel Former IESG member
No Objection
No Objection () Unknown

                            
Alexey Melnikov Former IESG member
(was Discuss) No Objection
No Objection (2009-05-27) Unknown

                            
Dan Romascanu Former IESG member
No Objection
No Objection () Unknown

                            
Jari Arkko Former IESG member
(was Discuss) No Objection
No Objection (2009-05-21) Unknown
> 1. Binary ID (or serial number)

Do people really register these using the binary representation?
Perhaps you mean numeric, not binary. On the wire the number may
be binary, but the IANA registry, for instance, uses hexadecimal
representation. (http://www.iana.org/assignments/megaco-h248)
Lisa Dusseault Former IESG member
No Objection
No Objection () Unknown

                            
Magnus Westerlund Former IESG member
No Objection
No Objection () Unknown

                            
Ralph Droms Former IESG member
No Objection
No Objection () Unknown

                            
Ron Bonica Former IESG member
No Objection
No Objection () Unknown

                            
Ross Callon Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
(was Discuss) No Objection
No Objection (2009-05-19) Unknown
  
  From the Gen-ART Review by Pete McCann ...

  Section 4:

  OLD:
     As at this date
  NEW:
     As of this date


  OLD:
     As H.248 is a master slave protocol if the malicious
  NEW:
     As H.248 is a master slave protocol, if the malicious


  OLD:
     there would be no affect
  NEW:
     there would be no effect


  Section 6.2:

  OLD:
     On the request for an Error Code registration, the IANA shall forward
     thr received information (i.e. the Error Code text (Specification
     required) to the IESG appointed expert for review (See section 4.3).
  NEW:
     On the request for an Error Code registration, the IANA shall forward
     the received information (i.e. the Error Code text and required
     specification) to the IESG appointed expert for review (See section 4.3).


  Section 6.3:

  OLD:
     On the request for an Error Code registration, the IANA shall forward
     the received information (i.e. the Service Change Reason text
     (Specification required) to the IESG appointed expert for review (See
     section 4.4).
  NEW:
     On the request for an Error Code registration, the IANA shall forward
     the received information (i.e. the Service Change Reason text
     and required specification) to the IESG appointed expert for review (See
     section 4.4).
Tim Polk Former IESG member
No Objection
No Objection (2009-05-21) Unknown
I support Alexey's Discuss.