Finding Fibre Channel over TCP/IP (FCIP) Entities Using Service Location Protocol version 2 (SLPv2)
draft-ietf-ips-fcip-slp-09
Yes
(Allison Mankin)
No Objection
(Alex Zinin)
(Bill Fenner)
(David Kessens)
(Harald Alvestrand)
(Jon Peterson)
(Margaret Cullen)
(Russ Housley)
(Scott Hollenbeck)
(Steven Bellovin)
Abstain
Note: This ballot was opened for revision 09 and is now closed.
Allison Mankin Former IESG member
Yes
Yes
()
Unknown
Alex Zinin Former IESG member
No Objection
No Objection
()
Unknown
Bert Wijnen Former IESG member
No Objection
No Objection
(2004-05-13)
Unknown
draft-ietf-ips-fcip-slp-09.txt has text that is "right justified"
Bill Fenner Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Harald Alvestrand Former IESG member
No Objection
No Objection
()
Unknown
Jon Peterson Former IESG member
No Objection
No Objection
()
Unknown
Margaret Cullen Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Scott Hollenbeck Former IESG member
No Objection
No Objection
()
Unknown
Steven Bellovin Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Ted Hardie Former IESG member
(was Discuss)
Abstain
Abstain
(2004-05-11)
Unknown
This document references the snmp: URI scheme, and it needs a reference to the appropriate document (draft-black-snmp-uri-04.txt). It could probably be informative, since the snmp: uri is only in the examples, but since it is not yet a registered scheme, some reference seems to be required. They have updated the section on NAT handling and NAPTs, and since they have added text that this probably won't work through a NAT/NAPT, I've shifted from DISCUSS to ABSTAIN. But I note that this document still has some broken assumptions. They've added this text: Configure the NAPT device to provide default mapping(s) for the well-known port(s) and use the default IANA-assigned FCIP TCP port number in service URLs, when possible. Apparently in response to my original question: >I don't think I understand how the first one helps (is there some default >mapping through NAPTs presumed for well known ports?) pointing to this text in the original: - Use the default IANA-assigned FCIP TCP port number in service URLs, when possible. The problem remains that unless the party outside the NAPT knows what the mapping will be and to use it instead of the port assigned, it won't work. I was asking if they thought there was some default mapping between the well known port and the port that a NAPT would select--trying to get them to see that there isn't such a thing and that this was broken. They've chosen to say "use a default mapping", but any such mapping would be local convention and knowable only by some out of band mechanism. You would have to say "turn off port translation for this port".