429RE: [bacnet-ip-wg] Network Ports [1 Attachment]
- Jul 18 8:11 AM
Sorry for the delay in getting to this.
Overall, I like the direction and your proposed changes. I especially like that it won’t prevent the NPO from going out as is.
I’m in favor of the hierarchical concept and it seems to address the concerns you voiced in Seattle. One minor comment, though: instead of PROTOCOL for the Port_Type, does DATA_LINK make sense?
The only comment I have about dropping the BACnet_ prefix is that “IP_” should now be “IPv4_”. Unless you were being sarcastic, I don’t think that proposed change, in light of your other proposed changes, is controversial at all. The history is that BACnet_IP_* was named as such because Annex J uses BACnet/IP throughout. But, since we’re moving towards allowing more agnostic elements, then I’m all for getting rid of “BACnet_” in the property names for both IPv4 and IPv6.
Since you suggested we let Draft 5 go as is, I don’t feel we have a pressing need to resume teleconferences at this point. Thoughts?
[Attachment(s) from Carl Neilson included below]
In Seattle I promised to get a proposal for your review on how we could allow the NPO to handle complex network setups.
Here is that proposal building Dave Robin’s idea of having hierarchical NPOs.
After fleshing this out, I am relatively confident that we can let the NPO go forward as is, and achieve our goals via changes in a future addendum.
I look forward to hearing everyone’s opinions on the proposed direction.
One controversial change that I do suggest is renaming all of the IP settings which are not BACnet specific by removing the “BACnet_” prefix.
Chair, SSPC 135 (aka The BACnet Committee)
- << Previous post in topic Next post in topic >>