Ask a questionAsk a question
 

Answer[MS-OXORULE] PidTagRuleCondition confusion

  • Friday, October 02, 2009 4:54 AMBrad Hards Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    In MS-OXORULE v20090712, Section 2.2.1.3.2.9 "PidTagRuleCondition", the condition associated with a rule is shown as type PtypServerEntryId.

    In MS-OXPROPS v20090712, Section 2.1022 "PidTagRuleCondition" contains "Data type: PtypServerEntryId, 0x00FD"

    In MS-OXCDATA v20090712, Section 2.12.1 "Property Value Types" says that 0x00FD is PtypRestriction, which "Table Variable size, a byte array representing one or more Restriction structures as specified in section 2.13."

    MS-OXCDATA describes the Restrictions (Section 2.13) and PtypServerId (2.12.1.3), but doesn't seem to mention PtypServerEntryId.

    Is there any more explanation on this?

    Brad



Answers

  • Wednesday, October 21, 2009 5:24 PMDominic Salemno MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Brad,

     

    PtypServerEntryId (0x00FD) was changed to PtypRestriction. OXCDATA and OXPROPS are consistent and accurate in its use of PtypRestriction. OXORULE is incorrect and needs to be modified to have PtypServerEntryId changed to PtypRestriction in PidTagRuleCondition (Section 2.2.1.3.2.9), and PtypServerEntryId changed to PtypRuleAction in PidTagRuleActions (Section 2.2.1.3.2.10).

     

    Is this information sufficient?

     

    Dominic Salemno

    Senior Support Escalation Engineer

    US-CSS DSC Protocols Team

  • Wednesday, November 04, 2009 7:19 PMTom Jebo_DSCMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Brad,

    The corrections to these three tag descriptions have been made and are now available in the newly published MS-OXPROPS version.  For convenience, here are the new sections:

    2.1060   PidTagRuleActions
    Canonical name: PidTagRuleActions
    Property ID: 0x6680
    Data type: PtypRuleAction, 0x00FE
    Area: Server-Side Rules Properties
    References:[MS-OXODLGT], [MS-OXORULE]
    Alternate names: PR_RULE_ACTIONS, ptagRuleActions

    2.1062   PidTagRuleCondition
    Canonical name: PidTagRuleCondition
    Property ID: 0x6679
    Data type: PtypRestriction, 0x00FD
    Area: Server-Side Rules Properties
    References: [MS-OXODLGT], [MS-OXORULE]

    2.1132   PidTagSentMailSvrEID
    Canonical name: PidTagSentMailSvrEID
    Property ID: 0x6740
    Data type: PtypServerId, 0x00FB
    Area: ProviderDefinedNonTransmittable
    References: [MS-OXCSTOR], [MS-OXOMSG]
    Alternate names: ptagSentMailSvrEID

    Notice that the section numbers have changed due to additional tags in the list.



    Best regards, Tom Jebo Senior Support Escalation Engineer Microsoft Open Specification Support

All Replies

  • Friday, October 02, 2009 12:29 PMSebastian CanevariMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Brad,

    Thank you for your help.

    Someone in my team will be looking into this and letting you know when we have a resolution.

    Thanks and regards,
    SEBASTIAN CANEVARI - MSFT Senior SEE Protocol Documentation Team
  • Friday, October 02, 2009 6:00 PMMark Miller_DSCMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Brad,

    Thank you for pointing out these issues in the document.  I will investigate and file the appropriate bugs and respond with more details on the last one you presented:

    MS-OXCDATA describes the Restrictions (Section 2.13) and PtypServerId (2.12.1.3), but doesn't seem to mention PtypServerEntryId.
     

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

  • Wednesday, October 07, 2009 10:30 PMBrad Hards Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Mark,

    Thanks for looking at this for me.

    Brad
  • Tuesday, October 20, 2009 11:06 AMBrad Hards Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Mark,

    How is this progressing?

    Brad
  • Wednesday, October 21, 2009 4:12 PMMark Miller_DSCMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Brad,

    A document bug was filed and it is being addressed.  I do not know a definitive time frame for when this will appear in the updated documentation at this point.

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

  • Wednesday, October 21, 2009 5:24 PMDominic Salemno MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Brad,

     

    PtypServerEntryId (0x00FD) was changed to PtypRestriction. OXCDATA and OXPROPS are consistent and accurate in its use of PtypRestriction. OXORULE is incorrect and needs to be modified to have PtypServerEntryId changed to PtypRestriction in PidTagRuleCondition (Section 2.2.1.3.2.9), and PtypServerEntryId changed to PtypRuleAction in PidTagRuleActions (Section 2.2.1.3.2.10).

     

    Is this information sufficient?

     

    Dominic Salemno

    Senior Support Escalation Engineer

    US-CSS DSC Protocols Team

  • Saturday, October 24, 2009 9:44 PMBrad Hards Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    I'm OK with the answer, but it looks like OXPROPS does need changes.

    I see (as of [MS-OXPROPS] — v20090712) the following entries:
    2.1020 PidTagRuleActions
    Canonical name: PidTagRuleActions
    Property ID: 0x6680
    Data type: PtypServerEntryId, 0x00FE
    Area: Server-Side Rules Properties
    References:[MS-OXODLGT], [MS-OXORULE]
    Alternate names: PR_RULE_ACTIONS, ptagRuleActions

    and

    2.1022 PidTagRuleCondition
    Canonical name: PidTagRuleCondition
    Property ID: 0x6679
    Data type: PtypServerEntryId, 0x00FD
    Area: Server-Side Rules Properties
    References: [MS-OXODLGT], [MS-OXORULE]
    Alternate names: PR_RULE_CONDITION, ptagRuleCondition
  • Monday, October 26, 2009 2:27 AMDominic Salemno MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Brad,

    Thank you for this information. It also seems that PtypServerEntryId is also referenced in the following Section as well:

    2.1091   PidTagSentMailSvrEID
    Canonical name: PidTagSentMailSvrEID
    Property ID: 0x6740
    Data type: PtypServerEntryId, 0x00FB
    Area: ProviderDefinedNonTransmittable
    References: [MS-OXCSTOR], [MS-OXOMSG]
    Alternate names: ptagSentMailSvrEID

    I will file three bugs against the documentation to resolve these issues.

    Dominic Michael Salemno
    Senior Support Escalation Engineer
    US-CSS DSC Protocols Team
  • Monday, October 26, 2009 10:49 AMBrad Hards Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Dominic,

    Note that that version is the 0x00FB variant, which does more closely match PtypServerId (See OXCDATA 2.12.1.3 "The PtypServerId Type")

    Thanks again.

    Brad
  • Wednesday, November 04, 2009 7:19 PMTom Jebo_DSCMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Brad,

    The corrections to these three tag descriptions have been made and are now available in the newly published MS-OXPROPS version.  For convenience, here are the new sections:

    2.1060   PidTagRuleActions
    Canonical name: PidTagRuleActions
    Property ID: 0x6680
    Data type: PtypRuleAction, 0x00FE
    Area: Server-Side Rules Properties
    References:[MS-OXODLGT], [MS-OXORULE]
    Alternate names: PR_RULE_ACTIONS, ptagRuleActions

    2.1062   PidTagRuleCondition
    Canonical name: PidTagRuleCondition
    Property ID: 0x6679
    Data type: PtypRestriction, 0x00FD
    Area: Server-Side Rules Properties
    References: [MS-OXODLGT], [MS-OXORULE]

    2.1132   PidTagSentMailSvrEID
    Canonical name: PidTagSentMailSvrEID
    Property ID: 0x6740
    Data type: PtypServerId, 0x00FB
    Area: ProviderDefinedNonTransmittable
    References: [MS-OXCSTOR], [MS-OXOMSG]
    Alternate names: ptagSentMailSvrEID

    Notice that the section numbers have changed due to additional tags in the list.



    Best regards, Tom Jebo Senior Support Escalation Engineer Microsoft Open Specification Support